Akamai: Reporting Issues affecting URL Traffic and URL Responses reports
Affected components: Data Services - ReportingReporting
Timeline of updates
- identified
We are aware of an issue with the 'URL Traffic' and ‘URL Responses’ report related to reporting data unavailability. We have identified the cause of the issue, and a fix is being implemented. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. 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 the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
- identified
The data is slowly getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.
- identified
The data is getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.
- monitoring
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/0D5a7000018q2TuCAI. We will continue to monitor to ensure that the impact has been fully mitigated.
- resolved
We can confirm that the issue was mitigated 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/0D5a7000018q2TuCAI 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).