Property Manager Property Activation Errors
We became aware of an issue with Property Manager related to activating properties with errors indicating "cloudlet policy not found or not valid" blocking some property activations. The issue lasted between approximately 15:30 UTC on November 3, 2026 and 17:15 UTC on November 3, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.
The latest update from Akamai.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Akamai
We became aware of an issue with Property Manager related to activating properties with errors indicating "cloudlet policy not found or not valid" blocking some property activations. The issue lasted between approximately 15:30 UTC on November 3, 2026 and 17:15 UTC on November 3, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.
Affected components
2Akamai in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
58
Median duration
19 h 50 min
This incident
100% shorter than the median
Other Akamai incidents
All incidentsAkamai·Customer Security Advisory: CVE-2026-98432
The Akamai Customer Community does not work. This problem also affects the Customer Service, Documentation and Community component. Akamai reports that it continues to investigate the problem.
Akamai·Performance Degradation for Customers in Mumbai and Chennai
Akamai reports performance degradation for customers in Mumbai and Chennai. The affected components are Edge Delivery and Content Delivery - Edge Delivery. Akamai is investigating, and the packet loss has subsided.
Akamai·Enterprise Application Access (EAA) Connector Issues
We can confirm that the issue was mitigated at 08:30 UTC on 27 October 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/0D5a700001bU4YFCA0 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.
Akamai·Edge Delivery issues between Indonesia and Singapore
Edge Delivery does not work correctly between Indonesia and Singapore. Content Delivery - Edge Delivery is affected. Akamai reports that the state is monitoring.
Akamai·Customer Security Advisory: Brotli Remote Code Execution Vulnerabilities
Akamai reports a Brotli remote code execution vulnerability that affects the Akamai Customer Community and related Customer Service, Documentation and Community components. Akamai resolved the issue on November 3, 2026, after about 11 days.
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.
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.cc/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.
https://outages.cc/feed.xml?providers=akamai/feed subscribe https://outages.cc/feed.xml?providers=akamaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane