Wrangler Deployments, Pages, and Workers Builds failures
Cloudflare reports that Wrangler deployments do not work and uploads can fail. The fail also affects Pages and Workers Builds. Cloudflare identified the problem and put a fix in place. Cloudflare now monitors the results.
State
Monitoring
Started
Ongoing for
19 min
Worst impact
Degraded
Timeline
2 updatesIdentified
7 min 38%
Monitoring
12 min 62%
Updates
Times in UTCAs posted by Cloudflare
A fix has been implemented and we are monitoring the results.
Cloudflare is investigating an issue with Wrangler deployments, users may suffer from failed uploads. We are working to analyse and mitigate this problem. More updates to follow shortly.
Affected components
5Cloudflare in the last 90 days
Full historyIncidents in 90 days
73
Days with an incident
71
Median duration
1 h 33 min
This incident
80% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Network Performance Issues in Singapore
Cloudflare reports network performance issues in the Singapore region (SIN). Cloudflare now monitors the situation for further issues. The incident started 40 minutes ago and is not resolved.
Cloudflare·Workers Builds Issues
Cloudflare Workers Builds had degraded performance. The incident is resolved. It lasted 29 minutes.
Cloudflare·Network disruption across multiple colocations in India
Cloudflare reported a network disruption across multiple colocations in India. The disruption degraded Cloudflare services in the region and affected Cloudflare R2 in Asia Pacific. Cloudflare identified 9 impacted colocations in India and removed them from the network. The incident is resolved and lasted 72 minutes.
Cloudflare·Increased Errors for Durable Objects in Western Europe
Cloudflare reported increased errors for Durable Objects in Western Europe. The incident is resolved and it lasted about 19 hours and 41 minutes.
Cloudflare·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.
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