Cloudflare Workers experienced a 1.6-hour observability issue where a subset of customers could not see logs in the Workers Observability dashboard after deploying a new Worker version, though affected Workers continued to serve traffic normally with metrics still available. The root cause was identified and the triggering change was reverted, but Workers using Gradual Deployments required manual intervention — either adjusting traffic weight percentages or redeploying — to restore logging. Cloudflare also worked on an automated fix for remaining affected customers.
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