Skip to main content
Akamai

Reporting Issues affecting URL Traffic and URL Responses reports

Degraded Lasted 12d 21h · started · Akamai's page

Level
confirmed
Worst impact
Degraded
Components
Reporting
Regions
us
Down Index
37of 100

What to do

  • Check whether you use Akamai Reporting in us. 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 12d 21h it lasted.

    Anything that failed between 2026-05-19 10:13 UTC and 2026-06-01 07:46 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

  1. identified

    We are aware of an issue with the 'URL Traffic' and ‘URL Responses’ report related to reporting data unavailability. We have identified the cause of the issue, and a fix is being implemented. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support) or the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  2. identified

    The data is slowly getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

    provider

  3. identified

    The data is getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

    provider

  4. monitoring

    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/0D5a7000018q2TuCAI. We will continue to monitor to ensure that the impact has been fully mitigated.

    provider

  5. resolved

    We can confirm that the issue was mitigated 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/0D5a7000018q2TuCAI 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-ccd0917800

Is Akamai still down?

No, this incident was resolved 2026-06-01 07:46 UTC. For Akamai's live state, see https://down.guide/akamai.

How long did it last?

12d 21h, from 2026-05-19 10:13 UTC to 2026-06-01 07:46 UTC, by the times Akamai posted.

What was affected?

Akamai named Reporting in us.

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.