Resolved after 1 hour 37 minutes, affecting Workers Observability, on August 7, 2026.
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.
Affected components
Update timeline
- investigating Aug 07, 2026, 04:04 PM UTC
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.
- identified Aug 07, 2026, 05:10 PM UTC
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.
- resolved Aug 07, 2026, 05:42 PM UTC
This incident has been resolved.
Your product runs on more than Cloudflare
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services