← Back to Fly.io History
minor✓ Resolved

Upstream network issues

Fly.ioWed, Sep 2, 2026, 02:18 PM
Status
resolved
Duration
1h 42m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, Sep 2, 2026, 04:01 PM
This incident has been resolved.
monitoringWed, Sep 2, 2026, 03:33 PM
A fix has been implemented and we are monitoring the results.
identifiedWed, Sep 2, 2026, 02:56 PM
We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.
identifiedWed, Sep 2, 2026, 02:48 PM
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.
identifiedWed, Sep 2, 2026, 02:18 PM
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.

📊 TECHNICAL DETAILS

Internal ID
78f392ec-c20f-408c-8930-235e6a1e09e4
External ID
200423xbd0kv
🕐 Started
Wed, Sep 2, 2026, 02:18 PM
🔄 Last Updated
Wed, Sep 2, 2026, 04:01 PM
✓ Resolved
Wed, Sep 2, 2026, 04:01 PM
MINOR
Impact Level
1h 42m
Total Duration
4
Status Updates
Affected Components
LAX - Los Angeles, California (US)SJC - San Jose, California (US)
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed