Multiple Compute and Edge Delivery Services Experiencing Packet Loss in India Region

What to do

• Check whether you use Akamai Edge Delivery in apac, in. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3d 20h it lasted.

  Anything that failed between 2026-02-27 21:32 UTC and 2026-03-03 17:32 UTC may need a replay.

• Subscribe to Akamai's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai 5

1. monitoringFeb 27, 2026, 9:32 PM UTC

   We became aware of a reoccurrence of the issue with a third-party service provider causing degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region related to https://www.akamaistatus.com/incidents/m5z1b82n5h0z. The issue lasted between 19:45 UTC and 21:00 UTC on February 27, 2026. We have taken mitigation steps and escalated to our third-party service provider to investigate the additional period of impact; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will continue to monitor to ensure that the impact has been fully mitigated. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

   provider

2. investigatingFeb 28, 2026, 11:16 AM UTC

   We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region. We are continuing to work with our third-party service provider to nvestigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will provide an update within the next 120 minutes.

   provider

3. investigatingFeb 28, 2026, 12:26 PM UTC

   We have been able to apply mitigation actions that improve the experience for customers connecting to the Mumbai, IN region, and continue working with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will provide an update as we make progress.

   provider

4. monitoringFeb 28, 2026, 5:43 PM UTC

   We have taken mitigation steps and escalated to our third-party service provider who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will continue to monitor to ensure that the impact has been fully mitigated.

   provider

5. resolvedMar 3, 2026, 5:32 PM UTC

   We can confirm that the issue was mitigated at 13:40 UTC on February 28, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS, or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.