outages.live
Live
CloudflareIncident ·

Changes to Cloudflare Workers are not producing Event Subscription events

DegradedOfficial update
0

Cloudflare Workers changes do not produce Event Subscription events. This affects Workers and Queues. Cloudflare reports that it is investigating. Cloudflare disabled the feature on purpose and is working to restore it.

State

Investigating

Started

Ongoing for

2 h 59 min

Worst impact

Degraded

Timeline

1 update
01:5302:3803:2304:0804:53
DegradedUpdate postedTimes in UTC

Investigating

2 h 59 min 100%

Updates

Times in UTC

As posted by Cloudflare

Investigating

Changes to Cloudflare Workers are temporarily not producing Event Subscription events. We have intentionally disabled this feature due to an on-going issue. We are actively working to restore it, but this, regrettably, may take a while. Changes to Workers themselves are working normally. Already deployed Workers are entirely unaffected.

Affected components

4
WorkersQueuesDeveloper Services - QueuesDeveloper Services - Workers

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

81

Days with an incident

75

Median duration

1 h 39 min

This incident

1.8× the median

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

56 days
median 1 h 39 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Network Performance Issues in Eastern North America

Cloudflare network performance was degraded in Eastern North America. The Network component was affected. Cloudflare reported the incident as identified, then monitored it. Cloudflare resolved the incident after about 3 hours and 38 minutes.

Resolved

Cloudflare·Changes made to Workers may be delayed or disrupted

Cloudflare reported that changes to Workers, such as creating, editing and deleting them, were delayed or disrupted. Deployed Workers were not affected. Cloudflare resolved the incident after about 9 hours and 31 minutes.

Resolved

Cloudflare·Spectrum Availability issues

Cloudflare Spectrum and Network Services - Spectrum had availability problems. Cloudflare reports that the incident is resolved. The incident lasted about 6 minutes.

Resolved

Cloudflare·Network Performance Issues in Chicago

Between 04:55-05:12 UTC 7th Dec Cloudflare experienced issues with network performance in Chicago.

Resolved

Cloudflare·Spectrum Availability Issue in Phoenix

Cloudflare Spectrum was degraded in Phoenix. The incident is resolved and lasted about 2 days and 14 hours.

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane