- Level
- confirmed
- Worst impact
- Operational
- Components
- Reporting
What to do
Check whether you use Akamai Reporting. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 6h it lasted.
Anything that failed between 2026-08-04 07:54 UTC and 2026-08-05 14:33 UTC may need a replay.Subscribe to Akamai's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai 5
- monitoring
We became aware of an issue with "Traffic by Hostname" related to reporting data availability. The issue lasted between 15:00 UTC on 3 August 2026 and 00:20 UTC on 4 August 2026. We have implemented a fix for this issue as of 00:20 UTC on 4 August 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will continue to monitor to ensure that the impact has been fully mitigated. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
provider
- monitoring
We are continuing to monitor to ensure that the impact has been fully mitigated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.
provider
- monitoring
Service remains operational. We are continuing to monitor the environment to ensure performance and stability are maintained.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.
provider
- monitoring
We are continuing to monitor the issue to ensure performance and stability are maintained. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.
provider
- resolved
We can confirm that the issue was mitigated at 00:20 UTC on August 4, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-68a44e59a7
Is Akamai still down?
No, this incident was resolved 2026-08-05 14:33 UTC. For Akamai's live state, see https://down.guide/akamai.
How long did it last?
1d 6h, from 2026-08-04 07:54 UTC to 2026-08-05 14:33 UTC, by the times Akamai posted.
What was affected?
Akamai named Reporting.
What caused it?
Akamai hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai's official status page, https://www.akamaistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.