Fly.io incident: Upstream network issues

1. resolvedSep 2, 2026, 15:57 UTC

   This incident has been resolved.

2. monitoringSep 2, 2026, 15:33 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedSep 2, 2026, 14:56 UTC

   We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.

4. identifiedSep 2, 2026, 14:48 UTC

   We have put in some temporary mitigations along with our providers. However since the root cause of this issue lies within a bigger upstream transit provider, you may continue to see some elevated latency and connection issues in/around affected regions. We're still working closely with them to resolve the root cause.

5. identifiedSep 2, 2026, 14:18 UTC

   We have observed an upstream network issue in LAX. Connections to some destinations may see elevated latency and packet loss. We're working with our upstream to resolve this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Fly.io'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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• Cursor: Investigating service degradation — Automations, Cloud Agents, Review AgentsMajor · Sep 2, 2026, 14:50 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• dbt Cloud: Delayed metadata ingestion and Discovery API latencyMinor · Sep 2, 2026, 15:00 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