Resolved after 1 hour 58 minutes, affecting LAX - Los Angeles, California (US) and SJC - San Jose, California (US), on May 28, 2026.
We are continuing to monitor for any further issues.
Affected components
Update timeline
- investigating May 28, 2026, 09:08 PM UTC
We are currently investigating increased latency in SJC.
- 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.
- 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.
- monitoring May 28, 2026, 10:33 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 28, 2026, 10:34 PM UTC
We are continuing to monitor for any further issues.
- resolved May 28, 2026, 11:07 PM UTC
This incident has been resolved.
Your product runs on more than Flightcontrol
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services