Observability ingestion delay and query failures
Cloudflare Workers Observability and Cloudflare Traces had delays in new data ingestion and increased query errors. The incident affected the Workers and Workers Observability components. Cloudflare reports that the incident is resolved, and it lasted about 5 hours and 26 minutes.
State
Resolved
Started
Lasted
5 h 26 min
Worst impact
Degraded
Timeline
3 updatesIdentified
4 h 54 min 90%
Monitoring
31 min 10%
Updates
Times in UTCAs posted by Cloudflare
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Cloudflare has identified an issue impacting Observability ingestion and querying. Customers may be seeing delays in new data coming in and increased error rates querying Workers Observability and Cloudflare Traces data. We are working to analyze and mitigate this problem. More updates to follow shortly.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
123
Days with an incident
85
Median duration
1 h 30 min
This incident
3.6× the median
Other Cloudflare incidents
All incidentsCloudflare·R2 and Durable Objects availability issues
R2 and Durable Objects in Eastern North America have intermittent errors and failed requests. Cloudflare reports that a fix is in place and monitoring is in progress.
Cloudflare·Durable Objects and D1 – Increased Errors
Cloudflare reported increased errors and latency on Durable Objects and D1 for a subset of customers; Workers that do not use these components were not affected. Cloudflare identified the problem and implemented a fix. The incident is resolved and lasted about 32 minutes.
Cloudflare·Cloudflare Access Issue
Cloudflare Access had degraded performance that can cause authentication failures for applications that strictly validate token claims. Cloudflare reports that the incident is resolved and lasted 2 hours and 8 minutes.
Cloudflare·Degraded connectivity between Europe and Asia Pacific
Cloudflare reported degraded connectivity between Europe and Asia Pacific. This affected Cache Reserve, D1, and R2. Cloudflare reported the incident as resolved after 4 hours and 53 minutes.
Cloudflare·Increased latency on Analytics API (GraphQL) queries
Cloudflare reports increased latency on Analytics API GraphQL queries. The incident is resolved and lasted about 2 hours and 47 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