- Level
- confirmed
- Worst impact
- Degraded
- Components
- St. Louis, United States - (STL)
- Regions
- us
Summary
Cloudflare says it has identified network performance issues in St. Louis (STL), USA. It says a fix has been implemented and it is monitoring the results.
Written by anthropic/claude-haiku-5.5 from Cloudflare's own updates.
What to do
Check whether you use Cloudflare St. Louis, United States - (STL) in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 20m it lasted.
Anything that failed between 2026-11-10 22:50 UTC and 2026-11-11 01:10 UTC may need a replay.Subscribe to Cloudflare's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Cloudflare 2
- monitoring
Cloudflare has identified issues with network performance in St. Louis (STL), USA. A fix has been implemented and we're monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-8335302066
Is Cloudflare still down?
No, this incident was resolved 2026-11-11 01:10 UTC. For Cloudflare's live state, see https://down.guide/providers/cloudflare.
How long did it last?
2h 20m, from 2026-11-10 22:50 UTC to 2026-11-11 01:10 UTC, by the times Cloudflare posted.
What was affected?
Cloudflare named St. Louis, United States - (STL) in us.
What caused it?
Cloudflare hasn't published a root cause. If it does, it shows here.
Where does this come from?
Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.