rewindex

CompaniesLinode (Akamai)Incidents

Linode (Akamai): Emerging Service Issue - Mumbai

No impact listedStatus: resolvedStarted Resolved (51 min)1 updatestatus.linode.com (opens in new tab)

Timeline of updates

  1. resolved

    The networking issue caused by an upstream problem with one of our peering partners has been resolved. The impacted regions were Mumbai (ap-west) and Mumbai 2 (in-bom-2), occurring between 1845 and 2000 UTC. If you continue to experience problems, please open a Support ticket for assistance.

From Linode (Akamai)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.linode.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Linode (Akamai), started 2025-05-16 19:51 UTC, resolved after 51 min, 1 update(s).

Title
Emerging Service Issue - Mumbai
Vendor
Linode (Akamai)
Date
URL
https://rewindex.com/company/linode-akamai/incidents/3kzrbv3gmcsj

Linode (Akamai) profileRecent Linode (Akamai) incidentsAll outages on May 16, 2025Linode (Akamai) in May 2025MarkdownJSON