DNS Malicious Filtering Issues

What to do

• Check whether you use Akamai Global Traffic Management 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 4h 22m it lasted.

  Anything that failed between 2026-03-10 17:38 UTC and 2026-03-10 22:00 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. investigatingMar 10, 2026, 5:38 PM UTC

   We are investigating an emerging issue with multiple Akamai products related to DNS malicious filtering where users may encounter fully qualified domain names (FQDNs) erroneously being flagged as malicious. 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. investigatingMar 10, 2026, 6:04 PM UTC

   We are continuing to investigate this issue. We identified that the components listed on this status page were incorrectly marked when the update was created. We have now corrected this to reflect the accurately impacted components. We apologize for any confusion this may have caused. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

   provider

3. identifiedMar 10, 2026, 6:50 PM UTC

   We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

   provider

4. identifiedMar 10, 2026, 8:08 PM UTC

   We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

   provider

5. monitoringMar 10, 2026, 9:03 PM UTC

   We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

   provider

6. resolvedMar 10, 2026, 10:00 PM UTC

   We can confirm that the issue was mitigated at 20:39 UTC on March 10, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.