ZAG (Zagreb) on 2026-11-05
We will be performing scheduled maintenance in ZAG (Zagreb) datacenter on 2026-11-05 between 02:00 and 04: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
Resolved
Starts
in 2 d
2026-11-05 02:00 UTC
Lasted
Not started
until 2026-11-02 18:03 UTC
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in ZAG (Zagreb) datacenter on 2026-11-05 between 02:00 and 04: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
53
Days with an incident
67
Median duration
1 h 15 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial outage that affects several locations. The affected locations include Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, Istanbul, Guatemala City, and Kyiv. Cloudflare is investigating the problem.
Cloudflare·Worker Deployments Delayed
Cloudflare Workers deployments were delayed. The incident affected Workers and Developer Services - Workers. Cloudflare reports that the incident is resolved. It lasted 49 minutes.
Cloudflare·Partial System Outage
Cloudflare reports a partial outage in 20 locations. The affected locations include Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, Istanbul, Guatemala City, and Chengmai. Cloudflare reports that the outage is resolved. It lasted about 43 hours and 33 minutes.
Cloudflare·Cache purge delays in Qingdao Shandong, China
This incident has been resolved.
Cloudflare·Increased Errors for Browser Run
This incident has been 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.
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