Cloudflare incident: Network Performance Degradation — Asia-Pacific

Affected components

• Network

1. resolvedSep 29, 2026, 23:01 UTC

   This incident has been resolved.

2. identifiedSep 25, 2026, 08:50 UTC

   Cloudflare continues to mitigate intermittent connectivity degradation for a small subset of customers caused by significant degradation of capacity in the region.

3. identifiedSep 23, 2026, 18:44 UTC

   The issue has been identified and a fix is being implemented.

4. investigatingSep 23, 2026, 18:42 UTC

   Since September 21, 2026 at 02:20 UTC, multiple subsea cable outages have caused congestion between Tokyo and Singapore datacenters. We have rerouted traffic to reduce impact and are working with third-party vendors to restore capacity.

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.

• HashiCorp Vault: HCP Terraform Returning 404sCritical · Sep 23, 2026, 17:43 UTC
• Shippo: Axlehire Shipment and Tracking OutageCritical · Sep 24, 2026, 08:51 UTC
• Supabase: Permission errors in the Supabase DashboardCritical · Sep 24, 2026, 10:37 UTC
• Shippo: Elevated error rate on Canada Post ShipmentCritical · Sep 24, 2026, 19:23 UTC
• OpenAI: Issues with CodexCritical · Sep 25, 2026, 22:58 UTC
• Snowflake: INC20000237Critical · Sep 25, 2026, 23:00 UTC
• Fly.io: Network outage in AMS regionCritical · Sep 26, 2026, 20:10 UTC
• Figma: Service disruptionCritical · Sep 27, 2026, 01:04 UTC
• Snowflake: INC20000239Critical · Sep 27, 2026, 02:15 UTC
• Linear: EU sync failureCritical · Sep 27, 2026, 10:56 UTC

How often does Cloudflare have incidents?

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