Brief Cloudflare US East Slowdown
No widespread internet outage is in progress this Sunday morning (checked around 13:50 UTC). The one notable event so far was short and is resolved: a Cloudflare latency incident in the eastern United States.
**Cloudflare: latency and timeouts in Virginia and Ohio (resolved)**
From 08:00 to 08:50 UTC, Cloudflare customers served through its Ashburn, Virginia (IAD) and Columbus, Ohio (CMH) locations saw higher latency and timeouts. Cloudflare says an external provider unexpectedly withdrew prefixes on peering links in those cities. Service fully recovered once the prefix advertisements were restored. Ashburn is one of the busiest interconnection hubs in the world, so some users in the US East region may have noticed slow or failing sites for a while. The incident was posted after it ended. [Cloudflare incident](cloudflarestatus.com)
Cloudflare's status page also lists a number of individual data centers as degraded or re-routed. That is routine for Cloudflare's network, where traffic moves to nearby locations during maintenance. Its long-running WARP geolocation issue (open since August 27) is still marked as identified.
**Minor, ongoing**
**Recently resolved (past 72 hours)**
**All clear**
AWS, Google Cloud, Azure, GitHub, Akamai, Anthropic (Claude), Discord, Atlassian, Slack, Zoom, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, Replicate, ElevenLabs, Cohere and Stability AI all report normal operation. Searches of crowd-sourced outage reports turned up no major consumer platform outage today. Meta's status page could not be read automatically, and Fastly's status page blocks automated checks, so their status is based on the absence of public reports.
The internet is up.