Akamai: Account Protector Issues
Affected components: Account ProtectorApp & Network Security - Account Protector
Timeline of updates
- investigating
We are investigating an emerging issue with Account Protector. We are actively investigating the issue and will provide another update within the next 30 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/.
- 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/0D5a700001VNuHQCA1. We will provide an update within the next 60 minutes.
- investigating
We are continuing to investigate this issue. We will provide an update within the next 60 minutes.
- monitoring
We have implemented a fix for this issue as of 22:45 UTC on September 23, 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.
- resolved
We can confirm that the issue was mitigated at 22:45 UTC on September 23, 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/0D5a700001VNuHQCA1 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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).