Incidentsby GlyphUpstream network issues
Sep 2, 14:18 UTCSep 2, 15:57 UTC
Duration
1h 39m
Impact
Minor
Root cause
Network
Fly.io, 90 days
53 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 2, 15:57 UTC
This incident has been resolved.
- Monitoring · Sep 2, 15:33 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Sep 2, 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.
- Identified · Sep 2, 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.
- Identified · Sep 2, 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.
More from Fly.io
Full historyIPv6 egress issues on a subset of IAD hostslasted 23mEmergency network maintenance on a subset of hosts in ORDlasted 14mElevated Machine start failures in ARNlasted 1h 1mEmergency maintenance in IADlasted 38mOutbound IPv4 connectivity failures in ARN, JNB, and GRUlasted 2h 10mSlow image pulls delaying Machine starts in IADlasted 1h 28m