Akamai: Case Ticketing Issue
Affected components: Case TicketingCustomer Service, Documentation and Community - Case Ticketing
Timeline of updates
- investigating
We are investigating an emerging issue with a third-party service provider where users might experience issues creating new tickets with Akamai Support. The issue appears to have started around 08:00 UTC on Sep 16, 2026. The customers can use https://control.akamai.com/apps/support-ui/#/contact-support or reach out to country-specific support numbers for urgent cases. We are working with the service provider and actively investigating the issue and will provide another update within the next 60 minutes.
- investigating
We are continuing to work our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001U5jVxCAJ.
- monitoring
The third-party provider has implemented a fix for this issue as of 12:20 UTC on 16 Sep,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/0D5a700001U5jVxCAJ. We will continue to monitor to ensure that the impact has been fully mitigated
- resolved
We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ 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).