Skip to main content
Akamai

DataStream Configuration Issues

Degraded Lasted 1d 5h · started · Akamai's page

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

What to do

  • Check whether you use Akamai Log Delivery 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 1d 5h it lasted.

    Anything that failed between 2026-06-25 18:14 UTC and 2026-06-26 23:35 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 6

  1. investigating

    We are investigating an emerging issue with DataStream related to configuring and editing DataStream configurations with users possibly running into the following errors: "There are no eligible properties available to clone the stream.", "One or more properties are invalid. Provide properties that are authorized to be a part of this stream, and belong to the contract and group ID.". 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/group/0F90f000000DFgx/service-incident-notifications. 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/0D5a700001FiyHGCAZ. We will provide an update within the next 60 minutes.

    provider

  3. 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/0D5a700001FiyHGCAZ. Subsequent updates around mitigation status will be posted as progress is made.

    provider

  4. monitoring

    We have rolled back a release which we believe may have caused this issue as of 20:55 UTC on 25 June 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/0D5a700001FiyHGCAZ. We will continue to monitor to ensure that the impact has been fully mitigated.

    provider

  5. monitoring

    We are actively monitoring the fix for this issue and will share updates on mitigation status as progress continues. Thank you for your patience.

    provider

  6. resolved

    We can confirm that the issue was mitigated at 20:55 UTC on 25 June 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/0D5a700001FiyHGCAZ, 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-708d44e193

Is Akamai still down?

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

How long did it last?

1d 5h, from 2026-06-25 18:14 UTC to 2026-06-26 23:35 UTC, by the times Akamai posted.

What was affected?

Akamai named Log Delivery 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.