Akamai's Control Center and Configuration Deployment system broke for 1h 4m on 29 September 2026. If you tried to activate a delivery configuration or manage users in Control Center during that window, the fault was on Akamai's side, not yours.
Started
20:28 UTC
Duration
Lasted 1h 4m
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: Akamai Control Center, Configuration Deployment
What happened?
Akamai opened the incident at 20:28 UTC, reporting an emerging issue with Configuration Deployment that caused errors when activating delivery configurations in Property Manager. At 20:48 UTC Akamai added a second, related problem: customers could not access Identity Manager to manage their users inside Control Center. Both issues sat under the same incident and the same timeline. Akamai pointed customers with a valid Control Center login to its community status page for more detail, which is not visible to anyone without that login. At 21:22 UTC Akamai marked the incident resolved, stating the issue had actually been mitigated at 20:25 UTC, three minutes before the first public update went out. That gap between the internal mitigation time and the public posting time is on the record as written, not an estimate. Akamai's own updates give no cause beyond the symptom description: no root cause, no mention of what changed or broke internally. No post-mortem has been published beyond the resolution note, and Akamai's statement about "continuous improvements to prevent a recurrence" does not specify what will change. No user reports were filed during the window on this page. The affected components were Control Center and Configuration Deployment, out of two components listed for the day, and no other incident was logged for Akamai on 29 September 2026.
Learning
UptimeRobot's own probes, which check edge reachability from the EU and North America every 60 seconds, stayed at 100% uptime through this window, and that is not a contradiction. The outage was in Akamai's control plane, the systems behind configuration activation and account management in Control Center, not in the edge network that serves your cached content to visitors. A probe that only checks whether content is reachable at the edge has no way to see a failure in the deployment or identity layer sitting behind it. This is the shape worth recognising: your product can look completely healthy to an external check while the tools you need to change or manage it are down behind the scenes. Akamai's history shows this kind of incident is not rare, 27 incidents in the last 90 days with a median duration of over 17 hours, far longer than this one's 1h 4m. Watching your own endpoints tells you whether your site is up, it does not tell you whether your provider's console is working. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
