Cloudflare Workers and Pages build errors
Cloudflare Workers Builds has build failures and longer queue times for some customers. Cloudflare identified the problem.
State
Identified
Started
Ongoing for
2 h 5 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
31 min 25%
Identified
1 h 33 min 75%
Updates
Times in UTCAs posted by Cloudflare
Customers may experience increased queue times for Workers Builders
Cloudflare is aware of and investigating an issue with Cloudflare Workers and Pages build failures which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
61
Days with an incident
68
Median duration
1 h 15 min
This incident
1.7× the median
Other Cloudflare incidents
All incidentsCloudflare·Increased Durable Object Errors in the Dallas, TX US region
Cloudflare reported increased errors from Durable Objects in the Dallas, Texas, USA region. Cloudflare monitored the issue and then resolved it. The incident lasted 64 minutes.
Cloudflare·Elevated number of 5xx errors in HKG
Between 06:20-6:32 UTC customers reaching Hong Kong may have experienced an elevated number of 5xx errors or CNI timeouts due to congestion.
Cloudflare·Partial System Outage
Cloudflare reported a partial outage in 20 locations. These locations include Accra, Albuquerque, Arica, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Manama, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, and Istanbul. The incident is resolved, and it lasted 531 minutes.
Cloudflare·Network Performance Issues in APJC
Cloudflare reported network performance issues in the APJC region. The Network component was degraded. Cloudflare identified the issue, implemented a fix, and monitored the results. The incident is resolved and lasted about 72 minutes.
Cloudflare·Cloudflare Container Issues
Cloudflare Containers failed to start and showed an increased level of errors. Cloudflare reports that the incident is resolved. The incident lasted 71 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.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