Network Performance Issues in Ashburn, US
Cloudflare reports network performance issues in Ashburn, United States (IAD). Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted 67 minutes.
State
Resolved
Started
Lasted
1 h 7 min
Worst impact
Degraded
Timeline
3 updatesIdentified
13 min 20%
Monitoring
54 min 80%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
105
Days with an incident
82
Median duration
1 h 26 min
This incident
22% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Turnstile verification failures
Cloudflare Turnstile verification fails for some users who have browser fingerprinting protection enabled. Cloudflare identified the issue and a fix is in progress. The incident started 20 minutes ago and continues.
Cloudflare·Elevated number of 52x origin connectivity errors in Seoul
Between 04:50 - 05:50 UTC 17th November, customers in Seoul may have experienced an elevated number of 52x origin connectivity errors. This is now resolved.
Cloudflare·Network Performance Issues in Montreal, Canada
Cloudflare identified an issue that affected network performance in Montreal, Canada, between 20:10 and 20:40 UTC on November 16, 2026. During this time, customers may have experienced increased HTTP 499 errors and elevated latency. This incident has been resolved.
Cloudflare·Errors creating predictions for some models
Cloudflare reports that prediction creation failed for some models on Replicate. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted 109 minutes.
Cloudflare·Elevated number of errors in Bogotá
Between 01:30-03:00 UTC customers reaching Bogotá, CO may have experienced an elevated latency and a number of 4xx errors.
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.
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.
https://outages.live/feed.xml?providers=cloudflare/feed subscribe https://outages.live/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane