F5 incident

F5 Distributed Cloud - Service Interruption - Intermittent Latency spikes and timeouts reported in India region- INC-20260626-479

Minor Resolved View vendor source →

F5 experienced a minor incident on June 26, 2026 affecting Mumbai, India and Chennai, India, lasting 5h 15m. The incident has been resolved; the full update timeline is below.

Started
Jun 26, 2026, 11:58 AM UTC
Resolved
Jun 26, 2026, 05:14 PM UTC
Duration
5h 15m
Detected by Pingoru
Jun 26, 2026, 11:58 AM UTC

Affected components

Mumbai, IndiaChennai, India

Update timeline

  1. investigating Jun 26, 2026, 11:58 AM UTC

    This advisory is to inform you that we are currently investigating reports of latency and intermittent timeouts with specific service provider. We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update. Investigation Status: • We have identified potential service impact at 11:50 AM UTC • Our incident response team has been fully mobilized; • Initial investigation and impact assessment efforts are underway. Next Steps: • A detailed incident notification will be provided within 30 minutes; • Our teams are working to determine the root cause of the incident; • We will share mitigation steps as soon as they become available. We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels. Thank you for your continued support and trust in F5.

  2. investigating Jun 26, 2026, 01:10 PM UTC

    F5 has received reports from customers in the India region about connectivity issues, including increased latency and request timeouts when accessing applications.We are actively monitoring the situation and will continue to provide updates as and when additional information becomes available.

  3. resolved Jun 26, 2026, 05:14 PM UTC

    We would like to provide an update on the previously reported connectivity issues affecting customers in the India region. The issue has now been resolved, and services have returned to normal operation. The disruption was caused by an external network fiber cut impacting connectivity between Singapore and India. We will continue to closely monitor the environment to ensure continued service stability. Thank you for your patience and understanding.

  4. postmortem Jun 26, 2026, 07:54 PM UTC

    ## **Root Cause Statement** The incident was caused by a **fiber cut on a major regional ISP’s network \(Airtel\) between Indonesia and India.** This disruption led to **widespread congestion throughout the region, and across multiple networks with dependencies on Airtel. F5’s network and infrastructure remained fully operational throughout the event and did not experience any outage or service degradation.** As a result of the fiber cut, **some Internet traffic to/from India and nearby regions was degraded, leading to increased latency, intermittent timeouts/packet loss, and slowness.** **Mitigation: Upon detection of the event, F5 implemented traffic engineering measures within the F5 Distributed Cloud backbone to re-route our traffic away from the fault in Airtel’s network,** deliberately avoiding the impacted network segment, reducing our exposure to the provider’s outage, and improving overall service performance for our customers.