SYD (Sydney) on 2026-11-10
We will be performing scheduled maintenance in SYD (Sydney) datacenter on 2026-11-10 between 14:00 and 20:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
The latest update from Cloudflare.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in SYD (Sydney) datacenter on 2026-11-10 between 14:00 and 20:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
77
Days with an incident
72
Median duration
1 h 33 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Network Performance Issues in Chicago
Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.
Cloudflare·Spectrum Availability Issue in Phoenix
Cloudflare reports an issue with Spectrum availability in Phoenix. This issue can degrade existing Spectrum applications. Cloudflare is monitoring the situation for further issues.
Cloudflare·Fedramp Customers have Delayed Purges
Cloudflare CDN Cache Purge has delayed purges for Fedramp customers. Stale content may be served until it expires. Non-Fedramp customers are not affected. Cloudflare identified the problem and continues to work on a fix.
Cloudflare·Partial System Outage
Cloudflare reported a partial system outage that affected 20 locations. These locations include Albuquerque, Sydney, Bangalore, Kyiv, and other points of presence. Cloudflare reports that the outage is resolved. It lasted 423 minutes.
Cloudflare·Wrangler Deployments, Pages, and Workers Builds failures
Cloudflare Wrangler deployments, Pages, and Workers Builds had failures in uploads. Cloudflare reported the incident as resolved. The incident lasted 21 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