Flightcontrol incident
Increased network latency in North America
Flightcontrol experienced a minor incident on June 11, 2026 affecting Management Plane - ORD and ORD - Chicago, Illinois (US), lasting 9h 56m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2026, 01:16 AM UTC
We are investigating elevated network instability across some hosts in ORD. Apps and managed postgres clusters on impacted hosts may see elevated latency or networking errors at this time.
- monitoring Jun 11, 2026, 01:59 AM UTC
Managed Postgres in ORD has returned to normal operation. We continue to see slightly elevated latencies and loss over transits in North America. We are working with our upstream network providers to improve performance.
- monitoring Jun 11, 2026, 03:30 AM UTC
Impacted NA backbones have been sidestepped where possible, and we're continuing to monitor network health.
- monitoring Jun 11, 2026, 05:24 AM UTC
The network between our regions has been performing well for the majority of traffic. We're still continuing to monitor a few impacted routes in North America that may be seeing elevated latency and packet loss.
- identified Jun 11, 2026, 07:58 AM UTC
We are seeing a recurrence of elevated latency across some hosts in ORD impacting the MPG control plane and a subset of clusters there. We are working to address this.
- identified Jun 11, 2026, 09:35 AM UTC
We are working with our upstream network provider to address periodic loss of connectivity over transit in ord
- monitoring Jun 11, 2026, 10:09 AM UTC
Our upstream paths have been fixed. We are monitoring the results.
- resolved Jun 11, 2026, 02:12 PM UTC
This incident has been resolved.