Live

Network Performance Issues in Washington, DC datacenter (IAD)

0

Network performance is degraded in the Washington, DC datacenter (IAD) and affects the Network component. Cloudflare reports that a fix is in place and the service is under monitoring.

State

Monitoring

Started

Ongoing for

13 min

Worst impact

Degraded

Timeline

2 updates
20:3520:3820:4120:4520:48
DegradedUpdate postedTimes in UTC

Investigating

4 min 31%

Monitoring

9 min 69%

Updates

Times in UTC

As posted by Cloudflare

Monitoring

A fix has been implemented and we are monitoring the results.

Investigating

Cloudflare is investigating issues with network performance in Washington, DC datacenter (IAD). We are working to analyze and mitigate this problem. More updates to follow shortly.

Affected components

1
Network

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

127

Days with an incident

85

Median duration

1 h 30 min

This incident

85% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 30 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Cloudflare Dashboard and Cloudflare API service issues in EU region

The Cloudflare Dashboard and Cloudflare API have service issues in the EU region. Cloudflare reports that the incident is resolved and that it lasted 29 minutes. Cached file delivery through the Cloudflare CDN and the security features at the Cloudflare Edge were not affected.

Resolved

Cloudflare·Cache Purging Delays in Amsterdam

Cloudflare single-file cache purging by URL through the Dashboard or API was delayed in Amsterdam. Cloudflare reported the incident as resolved. It lasted 1 hour and 41 minutes.

Resolved

Cloudflare·Network Performance Issues in Miami

Network performance is degraded in Miami, United States (MIA). Cloudflare reports that the incident is resolved. It lasted about 9 hours and 27 minutes.

Resolved

Cloudflare·R2 and Durable Objects availability issues

R2 and Durable Objects had intermittent errors and failed requests in Eastern North America. Cloudflare implemented a fix and monitored the results. Cloudflare reports that the incident is resolved and it lasted 102 minutes.

Resolved

Cloudflare·Observability ingestion delay and query failures

Cloudflare Workers Observability and Cloudflare Traces had delays in new data ingestion and increased query errors. The incident affected the Workers and Workers Observability components. Cloudflare reports that the incident is resolved, and it lasted about 5 hours and 26 minutes.

Resolved

Follow Cloudflare

Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane