Live

Reporting Issues

0

Akamai reports that the URL Traffic report does not show data, and this affects Reporting and Data Services - Reporting. Akamai is still investigating the issue and gives no fix time. The outage started at 03:20 UTC on 20 November 2026 and is not resolved.

State

Investigating

Started

Ongoing for

1 h 2 min

Worst impact

Degraded

Timeline

2 updates
03:2003:3503:5104:0604:22
DegradedUpdate postedTimes in UTC

Investigating

1 h 2 min 100%

Updates

Times in UTC

As posted by Akamai

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/0D5a700001gM1g3CAC We will provide further updates as we make progress.

Investigating

We are investigating an issue with the 'URL Traffic' report related to reporting data unavailability. 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 the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Affected components

2
ReportingData Services - Reporting

Akamai in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

34

Days with an incident

63

Median duration

19 h 48 min

This incident

95% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 days
median 19 h 48 min
90 days agoToday

Other Akamai incidents

All incidents

Akamai·Configuration Deployment delays

Akamai reports delays to fast changes on multiple Fast Metadata Activation channels and to configuration deployment across Cloudlets, Edge Delivery and Edge DNS. Akamai identified the cause and implemented a fix. Akamai confirms that the issue was mitigated at 21:05 UTC on November 18, 2026, and the incident is resolved.

Resolved · 1 affected

Akamai·Customer Security Advisory: CVE-2026-114938

Akamai reports a major outage that affects the Customer Security Advisory and the Customer Service, Documentation and Community Customer Security Advisory components. Akamai is investigating the issue. Akamai is assessing the Java4Shell vulnerability CVE-2026-114938 and says its security teams are taking mitigation measures.

Major outage

Akamai·Edge Delivery Issues in Singapore and Japan Regions

Edge Delivery and Content Delivery Edge Delivery have degraded service in the Singapore and Japan regions. Akamai reports that it implemented a fix at approximately 23:00 UTC on November 18, 2026, and that service has resumed normal operations. Akamai continues to monitor the issue.

Degraded

Akamai·Application Load Balancer reporting availability issues

Akamai reports that Application Load Balancer reporting and Data Services - Reporting had availability errors. Akamai identified the cause and applied a fix. Akamai resolved the incident at 14:36 UTC on November 16, 2026, after about 10 hours and 48 minutes.

Resolved

Akamai·Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 module

Akamai reports a security advisory for a remote code execution vulnerability in the Apache HTTP Server HTTP/2 module. This affects the Customer Security Advisory component and the Customer Service, Documentation and Community advisory. Akamai is investigating the potential impact across its platform and infrastructure, and reports no evidence that the vulnerability has been exploited on any Akamai platform or product.

Major outage

Follow Akamai

Your coding agent knows when Akamai is down, and tells you when a failure is theirs, not yours. You can also get Akamai incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "akamai" and tell me if Akamai has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=akamai
Slack
/feed subscribe https://outages.live/feed.xml?providers=akamai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane