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.
State
Resolved
Started
Lasted
21 min
Worst impact
Degraded
Timeline
3 updatesIdentified
7 min 32%
Monitoring
14 min 68%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
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
74
Days with an incident
71
Median duration
1 h 33 min
This incident
77% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial outage across multiple locations, including Albuquerque, Chicago, Sydney, Bangalore, Nairobi, and other sites. Cloudflare is investigating the problem. The provider gives no cause and no workaround.
Cloudflare·Network Performance Issues in Singapore
Cloudflare reported network performance issues in the Singapore region (SIN). The incident is resolved. It lasted about 1 hour and 50 minutes.
Cloudflare·Workers Builds Issues
Cloudflare Workers Builds did not work correctly and this affected multiple customers. Cloudflare reports that the issue is resolved. The outage lasted 29 minutes.
Cloudflare·Network disruption across multiple colocations in India
Cloudflare reported a network disruption across multiple colocations in India. This disruption affected Cloudflare R2 and other Cloudflare services in the Asia Pacific region. Cloudflare identified 9 impacted colocations in India, removed them from the network, and resolved the incident after 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. It lasted about 19 hours and 41 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