Public Networking Issue Causing Loopback Routing on BOM2 Virtual Machines

Resolved·Partial outage

We’ve published a write-up of this incidentRead the write-up

Read it here

Affected components

Mar 17, 2026, 10:34 AM

10:52 AM

Updates

Write-up published

Read it here

Resolved

This issue has now been resolved. The root cause was a downstream provider routing issue affecting public networking for Virtual Machines in India (BOM2). Network connectivity has been restored and impacted services should be functioning normally.

Tue, Mar 17, 2026, 10:52 AM

Identified

We have identified the issue as a public routing problem in BOM2 affecting Virtual Machines. Some public traffic was incorrectly routed to loopback, which caused network connectivity failures for impacted

Tue, Mar 17, 2026, 10:36 AM(16 minutes earlier)

Investigating

We are currently investigating a networking incident affecting Virtual Machines in India (BOM2). Due to an issue in public networking, some traffic was incorrectly routing to loopback, which may be causing connectivity failures or unstable network access for impacted instances.

Our team is actively working on identifying the root cause and restoring normal networking behavior as quickly as possible.

Affected components

Virtual Machine → India (BOM2): Partial outage

A slightly cleaner version for the title:

Public Networking Degradation in BOM2

And a slightly more polished message:

We are investigating a public networking issue affecting Virtual Machines in India (BOM2). Because of a networking fault, some traffic was being routed to loopback unexpectedly, which may result in failed public connectivity or intermittent network issues for affected instances.

We are actively working on mitigation and will share further updates as we have them.

Tue, Mar 17, 2026, 10:34 AM