A subset of Cloudflare customers experienced missing logs in the Workers Observability dashboard following new Worker deployments, lasting approximately 1.7 hours. Worker execution and traffic were unaffected throughout, with metrics remaining available. The root cause was identified and the triggering change was reverted; customers using Gradual Deployments could immediately self-resolve by adjusting traffic weights or redeploying, with an automated fix rolled out for remaining affected users.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We have identified the root cause and reverted the impacted change. However, for the fix to apply to existing Workers utilizing Gradual Deployments, affected Workers must have their deployment traffic percentages adjusted or redeployed.
As a workaround, if you are currently impacted, you can immediately resolve the issue for your service by modifying the traffic weights of your Gradual Deployment (for example, shifting your active deployment weights from 50%/50% to 40%/60%, or redeploying your Worker).
We are actively working on an automated fix for all remaining affected customers and will provide another update once resolved.
Cloudflare is aware, and investigating reports where a subset of customers are not seeing logs in the Workers Observability dashboard after deploying a new version of a Worker. Affected Workers continue to run and serve traffic normally. Metrics remain available.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with