Fly.io incident

Increased latency in SJC

Minor Resolved View vendor source →

Fly.io experienced a minor incident on May 28, 2026 affecting LAX - Los Angeles, California (US) and SJC - San Jose, California (US), lasting 1h 58m. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 09:08 PM UTC
Resolved
May 28, 2026, 11:07 PM UTC
Duration
1h 58m
Detected by Pingoru
May 28, 2026, 09:08 PM UTC

Affected components

LAX - Los Angeles, California (US)SJC - San Jose, California (US)

Update timeline

  1. investigating May 28, 2026, 09:08 PM UTC

    We are currently investigating increased latency in SJC.

  2. monitoring May 28, 2026, 09:56 PM UTC

    We have implemented a mitigation for the issue and are monitoring for stability. This issue happened on the edge hosts in SJC, which means that any traffic near/around SJC would have been affected during the incident. We will provide a more detailed write-up on our Infra Log (https://fly.io/infra-log/) later once we have a better picture of the entire incident.

  3. identified May 28, 2026, 10:25 PM UTC

    We're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.

  4. monitoring May 28, 2026, 10:33 PM UTC

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

  5. monitoring May 28, 2026, 10:34 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 28, 2026, 11:07 PM UTC

    This incident has been resolved.