Akamai's Edge Delivery service began showing problems at 13:24 UTC on 2 October 2026, tied to a DNS record change that had not reflected to Akamai's Edge DNS. The issue is still open as of Akamai's last update, and the fault sits with Akamai's own DNS propagation, not with anything on your side.
Started
13:24 UTC
Duration
Ongoing
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
What happened?
Akamai posted its first update at 13:24 UTC, saying it was investigating an emerging issue with Edge Delivery. The stated cause, as Akamai described it, was that a record change on a master DNS server was not reflecting to Akamai's Edge DNS. That is a propagation problem inside Akamai's own DNS infrastructure, sitting upstream of anything a website operator controls. A second update followed at 13:53 UTC, saying only that Akamai was continuing to investigate and pointing to its community page for further detail. No third update has been filed, so the incident is still open with that 13:53 UTC line as the last word from Akamai. Akamai's own notes direct customers with a valid Control Center login to a separate community page for specifics, which means the public status page you are reading carries less detail than what paying Akamai customers can see. Only one component is listed as affected: Edge Delivery. No user reports were filed in this window on our side. Akamai's history shows this is not a rare event for the company: 28 incidents in the past 90 days, with a median duration of 17 hours 7 minutes, and 388 incidents all time at a rate of 6.3 a month. Those figures suggest this is a provider that logs incidents often and that some run long, though Akamai has not yet said how long this one will take.
Learning
Our own probes, which check edge-reachability from both the EU and North America every 60 seconds, show 100% uptime over the last 24 hours, 7 days and 30 days, and this incident has not registered against those checks. That is not a contradiction. A DNS record change failing to propagate to Akamai's Edge DNS can break specific delivery paths or specific domains without making every edge node unreachable from a synthetic probe sitting outside Akamai's network. Your own monitoring, watching your own endpoints, can look exactly as clean as ours did, because the fault lives inside Akamai's DNS layer rather than at the edge nodes your traffic actually hits. That is the general shape of this kind of failure: the breakage is real for affected customers, but it is narrow enough, or positioned upstream enough, that a from-the-outside reachability check doesn't trip on it. Over the last 30 days we have logged 12 Akamai incidents, 10 resolved, with a median resolved duration of 13h 48m, so slow resolution is a pattern here rather than a one-off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
