Resolved
Cloudflare · degraded service
Network Performance Issues in Seattle
Started 12 Oct 12:54 UTC, resolved 12 Oct 21:06 UTC: it lasted 8 h 12 min.
8 h 12 min
How long it lasted, from the provider's times
1Update posted
1Region named
6Other incidents at the same time · 1 possibly relatedWhat it affected
As the provider names itWhat the provider posted
Newest first- 12 Oct 21:06 UTCResolvedBetween 12:54 and 21:06 UTC on October 12, 2026, Cloudflare experienced an issue that affected network performance in Seattle. During this time, customers may have experienced degraded network performance. This incident has been resolved.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Elevated Errors in China Network Colos
- GitHub Incident with Actions, Pull Requests and Issues
- Cloudflare Cloudflare Workers API
- GitLab.com GitLab Duo Workflow Issues
- OpenAI Delayed Costs data in the Compliance API
Earlier incidents in the 14 days before
- Cloudflare: Cloudflare API service issuesService incident · 2 times, latest 9 Oct
- Cloudflare: Network Performance Issues in QueretaroService incident · 9 Oct
- Cloudflare: Cloudflare DNS Resolver 1.1.1.1 and Gateway DNS are having issues in SINService incident · 9 Oct
- Cloudflare: Network Performance Issues in SofiaService incident · 8 Oct
- Cloudflare: Network Performance Issues in KochiService incident · 2 times, latest 8 Oct
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.