Skip to content
OutageDeck

Incident detail

Upstream network issues

Resolved incidentMinor

Timeline window

to

Get alerted the next time Fly.io breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Fly.io alerts work

Timeline

Incident updates

Every update Fly.io posted, oldest to newest, exactly as it appeared on their official status page.

  1. 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.

  2. 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.

  3. 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.

  4. Monitoring

    A fix has been implemented and we are monitoring the results.

  5. Resolved

    This incident has been resolved.

Keep exploring

More from Fly.io

Neighboring incidents on Fly.io's timeline and the rest of their record on OutageDeck.

← Older incident

API background job queue failure

Newer incident →

Sprites API Partial Outage

All Fly.io incidentsFly.io live status