Skip to main content
Akamai

Application Load Balancer reporting availability issues

Degraded Lasted 6d 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 6d 21h it lasted.

    Anything that failed between 2026-07-16 04:21 UTC and 2026-07-23 02:06 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. investigating

    We are investigating an issue with Application Load Balancer (ALB) reporting related to availability with errors. We are actively investigating the issue and will provide another update within the next 60 minutes. 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/0D5a700001J1h4UCAR. 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 Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  2. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR. We will provide the next update as we make progress.

    provider

  3. monitoring

    We have implemented a fix for this issue as of 04:36 UTC on 16 July 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/0D5a700001J1h4UCAR. We will continue to monitor to ensure that the impact has been fully mitigated.

    provider

  4. monitoring

    We did not observe a recurrence, and the system looks stable. We continue to monitor to ensure that the impact has been fully mitigated. We will provide the next update as we make progress.

    provider

  5. resolved

    We can confirm that the issue was mitigated at 04:36 UTC on 16 July 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/0D5a700001J1h4UCAR 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-e26a73fb74

Is Akamai still down?

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

How long did it last?

6d 21h, from 2026-07-16 04:21 UTC to 2026-07-23 02:06 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.