Network latency issues in NRT
Cloudflare reported network latency issues in Tokyo, Japan (NRT) that affected the Network component. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and it lasted 114 minutes.
State
Resolved
Started
Lasted
1 h 54 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 21 min 71%
Identified
21 min 18%
Monitoring
12 min 11%
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.
We are currently investigating a network latency issue in NRT
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
67
Days with an incident
69
Median duration
1 h 36 min
This incident
1.2× the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial outage. The affected components include Albuquerque, Arica, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Manama, Curitiba, Luanda, Mombasa, Helsinki, Nairobi, Fuzhou, and Guatemala City. Cloudflare is investigating the problem.
Cloudflare·Partial System Outage
Cloudflare reported a partial system outage that affected 20 locations, including Albuquerque, Sydney, Dallas, Bangalore, and Nairobi. Cloudflare reports that the incident is resolved. The outage lasted about 18 hours.
Cloudflare·Increased Durable Object Errors in the Dallas, TX US region
Cloudflare Durable Objects had more errors than usual in the Dallas, TX US region. Cloudflare reports that the incident is resolved. The incident lasted about 64 minutes.
Cloudflare·Cloudflare Workers and Pages build errors
Cloudflare Workers Builds had build failures and longer queue times. The incident is resolved. It lasted about 4 hours and 51 minutes.
Cloudflare·Increased Latency and Errors for R2 and Downstream Services in Western North America (WNAM)
Cloudflare has resolved an issue affecting R2 and downstream services in the Western North America region. Some customers may have seen elevated latency and errors between approximately 13:00 and 22:15 UTC on November 3, 2026. This may also have affected downstream services such as Stream and Pipelines.
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.cc/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.cc/feed.xml?providers=cloudflare/feed subscribe https://outages.cc/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane