- Level
- confirmed
- Worst impact
- Degraded
- Components
- LAX - Los Angeles, California (US), SJC - San Jose, California (US)
- Regions
- us
- Down Index
- 22of 100
What to do
Check whether you use Fly.io LAX - Los Angeles, California (US), SJC - San Jose, California (US) in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 14m it lasted.
Anything that failed between 2026-09-02 14:18 UTC and 2026-09-02 15:33 UTC may need a replay.Subscribe to Fly.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Fly.io 5
- 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.
provider
- 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.
provider
- 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.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2017b56578
Is Fly.io still down?
No, this incident was resolved 2026-09-02 15:33 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
1h 14m, from 2026-09-02 14:18 UTC to 2026-09-02 15:33 UTC, by the times Fly.io posted.
What was affected?
Fly.io named LAX - Los Angeles, California (US), SJC - San Jose, California (US) in us.
What caused it?
Fly.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Fly.io's official status page, https://status.flyio.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.