Fly.io incident: Network issues in US West Coast

1. resolvedSep 12, 2026, 22:12 UTC

   This incident has been resolved.

2. monitoringSep 12, 2026, 21:57 UTC

   Private networking between Fly Machines is resolved, and most outbound connections are healthy. We're continuing to monitor the network, and some issues will still be expected from clients physically located in US West until upstream transit issues are resolved.

3. investigatingSep 12, 2026, 21:22 UTC

   We are investigating upstream network issues from US West Coast (SJC, LAX). Apps hosted in US West regions may experience higher latency or packet loss, and requests from clients physically located in US West may experience higher latency.

What APIStatus.watch saw

• Sep 12, 2026, 21:25 UTCoperational → degraded
• Sep 12, 2026, 22:00 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• MongoDB Atlas: Impaired Cluster operations in AWS me-central-1 and AWS me-south-1Major · Sep 3, 2026, 16:44 UTC
• Elasticsearch: Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch outputMajor · Sep 9, 2026, 20:44 UTC
• Anthropic: Degraded functionality for Claude Cowork on WindowsMajor · Sep 10, 2026, 15:54 UTC
• Shippo: Elevated error rate on Royal Mail_SF TrackingMajor · Sep 12, 2026, 21:47 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC

How often does Fly.io have incidents?

Fly.io reported 19 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 57 min. See Fly.io's uptime and incident history