Akamai's Edge Delivery service degraded in Canada for 23h 22m on 28 September 2026, with requests returning 0xx errors. Akamai has confirmed the fault sat with a third-party provider on their side, not with you.
Started
16:22 UTC
Duration
Lasted 23h 22m
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 opened the incident at 16:22 UTC, reporting performance degradation in Canada tied to Edge Delivery, with 0xx errors surfacing on affected requests. The only component listed is Edge Delivery, so the scope Akamai itself describes is narrow: one region, one function. A second update at 16:41 UTC added no new detail beyond pointing customers to the Akamai Community feed for logged-in partners. The resolution update, timestamped 15:43 UTC the following day, says Akamai's third-party service provider confirmed the issue was mitigated at 16:08 UTC on 28 September 2026 and that service had resumed normal operation. That is the full extent of the public record: three updates, no root cause beyond "third-party service provider," and no post-mortem published. Akamai does not name the provider or describe what failed in their stack. The stated duration of 23h 22m is long against Akamai's own history, though their 90-day median incident runs 17 hours 7 minutes, so this sits above typical but not off the scale for them. No user reports were filed during the window on this page. With a single company update chain and no independent confirmation, everything here rests on what Akamai chose to publish.
Learning
UptimeRobot's own probes against Akamai's edge-reachability component, run from EU and NA regions every 60 seconds, show 100% uptime across the last 24 hours, 7 days and 30 days, and this incident was not registered against our monitoring. That is not a contradiction. Akamai's incident was scoped to Edge Delivery performance in Canada specifically, a narrower and more regional problem than a full reachability failure, and external checks hitting edge endpoints from elsewhere can stay green while a geographically bounded degradation plays out. This is the general shape of a provider-side outage: the failure lives inside infrastructure you never touch, so pinging your own application or site tells you nothing about it. Over the last 30 days Akamai has logged 11 incidents with a median duration of 13h 48m, a pattern worth knowing if your product depends on their edge layer. Your own monitoring covers your half, the servers and code you run. UptimeRobot now watches the provider's half too, so next time something feels slow in one region, you know which side broke without guessing.
