Cloudflare incident: Network Performance Issues in Seattle

Affected components

• Seattle, WA, United States - (SEA)

1. resolvedOct 12, 2026, 21:06 UTC

   Between 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Cloudflare's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Anthropic: Elevated errors on platform.claude.comMajor · Oct 7, 2026, 13:25 UTC
• Shippo: UPS Tracking disruptionMajor · Oct 11, 2026, 03:22 UTC
• Telnyx: Email API messages rejected with gw_reject// injection_failedMajor · Oct 12, 2026, 08:31 UTC
• Grafana Cloud: Elevated Errors Ingesting Metrics in AWS US East (VA)Major · Oct 12, 2026, 09:45 UTC
• Vercel: Increased build and deployment failuresMajor · Oct 12, 2026, 13:35 UTC
• Contentful: [INCIDENT] https://www.contentful.com/developers/docs/ is not workingMajor · Oct 12, 2026, 18:22 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Twilio: SMS Delivery Delays and Failures from Twilio to Movistar El SalvadorMinor · Oct 6, 2026, 20:59 UTC

How often does Cloudflare have incidents?

Cloudflare reported 96 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 33m. See Cloudflare's uptime and incident history