---
title: "Degraded Performance – Ping Delays (NRT & BOM)"
description: "Resolved · affects 🇯🇵 Tokyo, Japan (Fly), 🇮🇳 Mumbai, India (Fly) · Jun 25, 2026"
base_url: "https://status.openstatus.dev"
canonical: "https://status.openstatus.dev/events/report/2282"
homepage_url: "https://openstatus.dev"
contact_url: "mailto:ping@openstatus.dev"
---

# Degraded Performance – Ping Delays (NRT & BOM)

[Status](/.md) › [Events](/events.md) › Degraded Performance – Ping Delays (NRT & BOM)

Jun 25, 2026 · 7 days ago · affects: 🇯🇵 Tokyo, Japan (Fly), 🇮🇳 Mumbai, India (Fly) · 4 minutes

## Updates

### + Resolved — Jun 25, 1:33 PM

affects: 🇯🇵 Tokyo, Japan (Fly) (operational), 🇮🇳 Mumbai, India (Fly) (operational)

The issue with our hosting provider has been resolved. Ping delays from our NRT (Tokyo, Japan) and BOM (Mumbai, India) Fly.io probes have returned to normal. All systems are operating as expected. We apologize for any inconvenience this may have caused.

### x Investigating — Jun 25, 1:29 PM

affects: 🇯🇵 Tokyo, Japan (Fly) (degraded performance), 🇮🇳 Mumbai, India (Fly) (degraded performance)

We are currently investigating increased latency and delayed pings originating from our NRT (Tokyo, Japan) and BOM (Mumbai, India) Fly.io probes. This appears to be related to an issue with our hosting provider. Our team is actively monitoring the situation and will provide further updates as they become available.