Akamai favicon

Akamai outage on 2026-10-27

akamaistatus.com
October 2026 27 Minor incident

Akamai filed two separate incidents on 27 October 2026. One hit a subset of Enterprise Application Access (EAA) Connectors for nearly six hours, the other caused performance degradation for customers in Mumbai and Chennai. Both faults sat on Akamai's side of the network.

Started

09:58 UTC

Duration

Lasted 5h 56m

Source

IsDown

Next time

Akamai is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Edge Delivery, Enterprise Application Access

What happened?

Akamai's first update, posted at 09:58 UTC, said it was investigating an issue affecting a subset of Unified EAA Connectors, and noted the problem had actually begun around 01:25 UTC, well before the filing. At 11:44 UTC Akamai said it had identified the cause and was implementing a fix, without stating what the cause was. The incident was marked resolved at 15:52 UTC, with Akamai confirming the issue was mitigated at 08:30 UTC, over seven hours earlier than the resolution notice. That gap between mitigation and the public resolution update is on Akamai's own timeline, not an estimate. The total duration logged for this incident is 5h 56m. A second, separate incident started at 13:09 UTC covering Mumbai and Chennai. Akamai said that between 08:05 UTC and 10:45 UTC, customers in those regions may have seen performance degradation caused by packet loss within an upstream provider's network. Akamai stated the loss had subsided by 10:45 UTC and said it would keep monitoring for recurrence for a few hours, but no further update has been filed, so this incident remains open on the record. No cause has been given for the EAA connector fault itself. No user reports were logged in this window for either incident.

Learning

UptimeRobot's own probes, which check edge reachability from EU and NA regions, show 100% uptime over the past 24 hours, 7 days and 30 days, with this incident not registered against them. That is not a contradiction. The EAA connector problem affected a subset of a specific access product, and the Mumbai and Chennai issue was about packet loss on an upstream network path, neither of which is the same thing as the general edge reachability that external checks from Europe and North America are built to catch. A green external check tells you the front door was open from where you measured, it does not tell you whether a specific connector pool or a regional path through an upstream provider was degraded. This is the common shape of these failures: narrow, regional or product-specific, and invisible to a broad reachability probe until a customer using that exact path or connector notices. Watching your own endpoints would only show you the symptom on your side, not whether Akamai's infrastructure was the cause. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.