Current answer
Fly.io experienced a minor incident: Upstream network issues. ServiceAlert observed recovery on Sep 2, 2026.
Looking for an update now? Check the current status, or follow Fly.io for future changes.
Incident Lifecycle
Affected Components
LAX - Los Angeles, California (US)
SJC - San Jose, California (US)
Incident Timeline
Monitoring
A fix has been implemented and we are monitoring the results.
Sep 2, 2026 at 3:33 PM UTC
Identified
We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.
Sep 2, 2026 at 2:56 PM UTC
Identified
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.
Sep 2, 2026 at 2:48 PM UTC
Identified
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.
Sep 2, 2026 at 2:18 PM UTC
Was your business affected by this Fly.io outage?
Follow Fly.io and route available status alerts to email or a team channel.