outages.live
Live
CloudflareIncident ·

Cloudflare Workers and Pages build errors

DegradedOfficial update
0

Cloudflare Workers Builds has build failures that can affect multiple customers. Cloudflare has identified the issue. Customers can see longer queue times for Workers Builders.

State

Identified

Started

Ongoing for

1 h 36 min

Worst impact

Degraded

Timeline

2 updates
14:4615:1015:3415:5816:22
DegradedUpdate postedTimes in UTC

Investigating

31 min 33%

Identified

1 h 5 min 67%

Updates

Times in UTC

As posted by Cloudflare

Identified

Customers may experience increased queue times for Workers Builders

Investigating

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

1
Workers Builds

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

61

Days with an incident

68

Median duration

1 h 17 min

This incident

1.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 17 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Increased Durable Object Errors in the Dallas, TX US region

Durable Objects return more errors than usual in the Dallas, TX US region. Cloudflare reports that the issue is under monitoring. The incident started 37 minutes ago.

Degraded

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.

Resolved

Cloudflare·Partial System Outage

Cloudflare reported a partial outage across 20 network locations, including Accra, Albuquerque, Sydney, Dallas, Bangalore, Nairobi and Istanbul. Cloudflare reports that the issue is resolved. The outage lasted 8 hours and 51 minutes.

Resolved

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. It lasted 72 minutes.

Resolved

Cloudflare·Cloudflare Container Issues

Cloudflare Containers failed to start and gave an increased level of errors. Cloudflare identified the problem and put a fix in place. The incident is resolved and it lasted 71 minutes.

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.cc/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane