Resolved
Cloudflare · degraded service
Bot Management Configuration Propagation Issues
Started 22 Sep 15:31 UTC, resolved 22 Sep 16:35 UTC: it lasted 1 h 3 min.
1 h 3 min
How long it lasted, from the provider's times
2Updates posted
4Other incidents at the same timeWhat it affected
As the provider names itWhat the provider posted
Newest first- 22 Sep 16:35 UTCResolvedWe have identified and applied an effective fix for this issue. This incident is now resolved.
- 22 Sep 15:31 UTCInvestigatingWe are currently investigating an issue where Bot Management configuration updates are not propagating to the edge. Our engineering team is aware of the issue and is actively working on a resolution. The running Bot Configuration at the Edge is not impacted. We will provide further updates as soon as we have more information.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
Earlier incidents in the 14 days before
- Cloudflare: Connectivity issues in Los Angeles (LAX)Service incident · 22 Sep
- Cloudflare: Partial visibility of Workers and Durable Objects analytics for Fedramp High customersService incident · 22 Sep
- Cloudflare: Network Performance Issues in San Jose (SJC-A)Service incident · 22 Sep
- Cloudflare: Network connectivity issues in LHR, LondonService incident · 22 Sep
- Cloudflare: Increased Cache FailuresService incident · 21 Sep
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about Cloudflare: its changes, known issues and incidents on one timeline.