Network issues in US West Coast
Sep 12, 21:22 UTCSep 12, 22:12 UTC
Duration
50m
Impact
Minor
Root cause
Not disclosed
Fly.io, 90 days
52 incidents
Affected
LAX - Los Angeles, California (US)SJC - San Jose, California (US)Regional Availability - LAX - Los Angeles, California (US)Regional Availability - SJC - San Jose, California (US)
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 12, 22:12 UTC
This incident has been resolved.
- Monitoring · Sep 12, 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.
- Investigating · Sep 12, 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.
More from Fly.io
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2416:31 UTC | State database issues in GRU | major | 2h 40m |
| Sep 2414:51 UTC | Private Networking issues (6PN) | major | 46m |
| Sep 2318:44 UTC | Partial Sprites outage | major | 7h 28m |
| Sep 2314:47 UTC | Elevated private networking errors | major | 36m |
| Sep 2312:42 UTC | Upstash unavailability in FRA region | major | 1h 22m |
| Sep 2306:18 UTC | IPv6 Networking Issues in DFW | major | 5h 57m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.