WSA reporting incomplete or missing data when filtering by TLS v3 Fingerprint

What to do

• Check whether you use Akamai Web Security Analytics 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 5d 3h it lasted.

  Anything that failed between 2026-04-23 14:11 UTC and 2026-04-28 17:39 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. investigatingApr 23, 2026, 2:11 PM UTC

   We are investigating an emerging issue with WSA where incomplete or missing data is reported when filtering by TLS v3 Fingerprint. 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. investigatingApr 23, 2026, 3:06 PM UTC

   We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a70000151eEnCAIWe will provide an update within the next 60 minutes.

   provider

3. investigatingApr 23, 2026, 3:56 PM UTC

   We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 120 minutes.

   provider

4. investigatingApr 23, 2026, 6:19 PM UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 3 hours.

   provider

5. investigatingApr 23, 2026, 9:50 PM UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notifications. Subsequent updates around mitigation status will be posted as progress is made.

   provider

6. resolvedApr 28, 2026, 5:39 PM UTC

   We can confirm that the issue was mitigated at 10:45 UTC on April 28, 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/0D5a70000151eEnCAI 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.