Missing Logs and Traces in Cloudflare Observability Platform
Between October 5 at 1:00 PM UTC and October 23 at 9:00 PM UTC, some customers may have experienced missing log events, incomplete traces, or inconsistent issue counts due to ingestion pipeline capacity limits. Traffic and Workers were not affected, and customers will not be billed for dropped events. Capacity has since been increased, and service has returned to normal.
The latest update from Cloudflare.
State
Resolved
Started
Lasted
18 days
Worst impact
Notice
Timeline
1 updateResolved
18 days 100%
Updates
Times in UTCAs posted by Cloudflare
Between October 5 at 1:00 PM UTC and October 23 at 9:00 PM UTC, some customers may have experienced missing log events, incomplete traces, or inconsistent issue counts due to ingestion pipeline capacity limits. Traffic and Workers were not affected, and customers will not be billed for dropped events. Capacity has since been increased, and service has returned to normal.
Cloudflare in the last 90 days
Full historyIncidents in 90 days
63
Days with an incident
68
Median duration
1 h 21 min
This incident
325× the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial outage. The problem affects some Cloudflare systems in 20 locations, including Accra, Albuquerque, Bangalore, Sydney, Dallas, Nairobi, and Fuzhou. Cloudflare is investigating the problem.
Cloudflare·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·Cloudflare Workers and Pages build errors
Cloudflare Workers Builds had build failures and longer queue times. The problem affected the Workers Builds component. Cloudflare reports that the incident is resolved. It lasted about 4 hours and 51 minutes. Customers with failed builds can retry in the Dashboard or push a new commit.
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.
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