Fly.io incident

Elevated control plane latency

Resolved after 3 hours 7 minutes, affecting BOM - Mumbai, India and NRT - Tokyo, Japan, on June 25, 2026.

monitoring Jun 25, 2026, 01:48 PM UTC

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

Started
Jun 25, 2026, 12:11 PM UTC
Resolved
Jun 25, 2026, 03:18 PM UTC
Duration
3h 7m
Detected by Pingoru
Jun 25, 2026, 12:11 PM UTC

Affected components

BOM - Mumbai, IndiaNRT - Tokyo, Japan

Update timeline

  1. investigating Jun 25, 2026, 12:11 PM UTC

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

  2. identified Jun 25, 2026, 01:20 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 25, 2026, 01:48 PM UTC

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

  4. resolved Jun 25, 2026, 03:18 PM UTC

    This incident has been resolved.

Your product runs on more than Fly.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →