← Back to Fly.io History
minor✓ Resolved

Elevated control plane latency

Fly.ioThu, Jun 25, 2026, 12:11 PM
Status
resolved
Duration
3h 9m
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Jun 25, 2026, 03:20 PM
This incident has been resolved.
monitoringThu, Jun 25, 2026, 01:48 PM
A fix has been implemented and we are monitoring the results.
identifiedThu, Jun 25, 2026, 01:20 PM
The issue has been identified and a fix is being implemented.
investigatingThu, Jun 25, 2026, 12:11 PM
We're addressing elevated control plane latency and saturation affecting the BOM and NRT regions. Apps with machines in this region might experience longer response times and possible timeouts (502 errors).

📊 TECHNICAL DETAILS

Internal ID
1d67846d-33be-4c9d-a4e5-d1cc4e88b021
External ID
dpv9bhyp19zr
🕐 Started
Thu, Jun 25, 2026, 12:11 PM
🔄 Last Updated
Thu, Jun 25, 2026, 03:20 PM
✓ Resolved
Thu, Jun 25, 2026, 03:20 PM
MINOR
Impact Level
3h 9m
Total Duration
3
Status Updates
Affected Components
BOM - Mumbai, IndiaNRT - Tokyo, Japan
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed