SJP (São José do Rio Preto) on 2026-11-04
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Cloudflare.
State
In progress
Started
Ongoing for
1 h 26 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
3 min 4%
In progress
1 h 22 min 96%
Updates
Times in UTCAs posted by Cloudflare
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Maintenance will begin soon as scheduled.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
68
Days with an incident
70
Median duration
1 h 33 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Increased Errors for Durable Objects and Downstream Services in Eastern North America (ENAM)
Cloudflare has resolved an issue affecting Durable Objects and downstream services in the Eastern North America (ENAM) region. Some customers may have seen elevated errors between approximately 21:20 and 21:22 UTC on November 4, 2026. This also affected downstream services such as R2.
Cloudflare·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·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.
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.
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