Akamai favicon

Akamai outage on 2026-11-16

akamaistatus.com
November 2026 16 Minor incident

Akamai's Application Load Balancer reporting had an availability issue lasting 10h 50m on 16 November 2026. The fault sat in Akamai's own reporting layer, not in anything you control.

Started

03:49 UTC

Duration

Lasted 10h 50m

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: Reporting

What happened?

Akamai opened the incident at 03:49 UTC, saying it was investigating an issue with Application Load Balancer (ALB) reporting tied to availability errors. The single affected component on record is Reporting, so this looks like a problem with how ALB availability data was being generated or surfaced, rather than a confirmed failure of the load balancer's traffic handling itself. A second update at 04:33 UTC repeated that investigation was ongoing, with no new detail beyond a pointer to Akamai's community feed. It took until 09:09 UTC, over five hours after the start, for Akamai to say it had identified a cause and was implementing a fix, though the public update does not say what that cause was. The incident was not marked resolved until 14:36 UTC, which stated the issue was mitigated at 13:37 UTC and that service had resumed normal operation. That puts the total duration at 10h 50m from first report to confirmed fix. Across the whole incident, Akamai published four updates, and none of them names a root cause beyond pointing customers to a community login for more detail. No user reports were filed during this window on our side. Akamai's own history shows this kind of incident is not rare: 30 incidents in the last 90 days, with a median duration of 22 hours 17 minutes, so this one resolved faster than Akamai's typical case even though it still ran most of a working day.

Learning

This incident is a good example of why a status page filing and an external uptime check can disagree without either being wrong. UptimeRobot's probes watch edge reachability from Europe and North America, checking every 60 seconds, and they recorded 100% uptime over the last 24 hours, 7 days and 30 days, with this incident never registering against those probes. That is consistent with what Akamai described: the fault was in ALB reporting, the layer that tells you and Akamai how your load balancer is performing, not in whether Akamai's edge was reachable or serving traffic. A reporting outage can run for nearly 11 hours while the actual request path stays healthy, which is exactly the kind of failure that pinging an endpoint from outside will never catch, because the endpoint itself never stopped answering. If your own monitoring only checks your application's edges, you would have seen green the whole time too, and rightly so, because your traffic was fine. The gap is visibility into Akamai's internal reporting pipeline, which neither your monitoring nor a simple reachability probe is built to see. 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.