Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Akamai down?

Akamai is having issues

Right now

Partly. Origin Server Connectivity Issues with Elevated Errors in APAC Region.

Last checked (2026-10-10 07:17 UTC) from www.akamaistatus.com · every 180s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/akamai/status.agent.json

MCP: upstream_status {"service":"akamai"}

CDN, edge DNS and security products.

What Akamai says

Degraded· 1 open incident

Taken as is from Akamai's own status page API. Incident titles and component names below are theirs.

Open www.akamaistatus.com

What UpButler measured

There is no keyless endpoint of Akamai that says anything useful, so UpButler does not probe it. To check your own Akamai account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Akamai

Text written by Akamai, shown unchanged.

Which part of Akamai?

Akamai components

1 of 42 not operational

Customer Service, Documentation and Community

  • Akamai Control CenterOperational
  • Akamai Customer CommunityOperational
  • Akamai Partner CommunityOperational
  • Akamai TechdocsOperational
  • Case TicketingOperational
  • ChatOperational
  • Diagnostic ToolsOperational
  • EmailOperational
  • TelephonyOperational

Content Delivery

  • CloudletsOperational
  • Edge DeliveryDegraded
  • Global Traffic ManagementOperational
  • Image ManagementOperational
  • NetStorageOperational

Data Services

  • Log DeliveryOperational
  • mPulseOperational
  • ReportingOperational
  • SIEM Data feedsOperational
  • TrafficPeakOperational
  • Web Security AnalyticsOperational

Configuration

  • Configuration DeploymentOperational
  • Content PurgeOperational
  • TLS Provisioning (Certificates, CPS)Operational

Enterprise Security

  • Akamai MFAOperational
  • Enterprise Application AccessOperational
  • Enterprise Application Access: API ServiceOperational
  • Enterprise Application Access: ConfigurationOperational
  • Enterprise Application Access: ReportingOperational
  • ETP/SIA: ClientOperational
  • ETP/SIA: ConfigurationOperational
  • ETP/SIA: ConnectorsOperational
  • ETP/SIA: Name ServersOperational
  • ETP/SIA: ReportingOperational
  • ETP/SIA: Web ProxyOperational

App & Network Security

  • Account ProtectorOperational
  • Akamai Identity CloudOperational
  • Bot ManagementOperational
  • Client-Side Protection & Compliance (formerly Page Integrity Manager)Operational
  • DNS Posture ManagementOperational
  • Edge DNSOperational
  • ProlexicOperational
  • Web Application FirewallOperational

Akamai incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: minor incident
  73. 2026-09-23: minor incident
  74. 2026-09-24: minor incident
  75. 2026-09-25: minor incident
  76. 2026-09-26: minor incident
  77. 2026-09-27: minor incident
  78. 2026-09-28: minor incident
  79. 2026-09-29: minor incident
  80. 2026-09-30: minor incident
  81. 2026-10-01: minor incident
  82. 2026-10-02: minor incident
  83. 2026-10-03: minor incident
  84. 2026-10-04: minor incident
  85. 2026-10-05: minor incident
  86. 2026-10-06: minor incident
  87. 2026-10-07: minor incident
  88. 2026-10-08: minor incident
  89. 2026-10-09: minor incident
  90. 2026-10-10: minor incident
2026-07-1319 of 19 days with an incidenttoday

Each bar is a day, coloured by the worst incident Akamai reported. It is their incident record, not a measurement of uptime.

Incidents
5
0 major or critical
Typical time to resolve
1 h 15 min
median
Nine in ten within
8 days
90th percentile
Longest
8 days
record since 2026-09-22
Started (UTC)IncidentImpactLasted
Edge Delivery Issuesminor1 h 15 min
Akamai Control Center and Configuration Deployment Issuesnoneunder a minute
Akamai Control Center and Configuration Deployment Issuesminor34 min
Edge Delivery issues in Canadaminor23 h 21 min
Increased latency during upstream provider maintenance in Singapore, Hong Kong, and Japanminor8 days

Get alerted when Akamai goes down

No account. One email when Akamai reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Akamai as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Akamai's current status in a README or an internal wiki. It updates by itself.

Akamai status badge

[![Akamai status](https://upbutler.com/status/akamai/badge.svg)](https://upbutler.com/status/akamai)

Tell your outage from Akamai's

Declare that your project depends on Akamai. When one of your monitors fails while Akamai has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - akamai
Ask before you retry
curl -s https://upbutler.com/status/akamai/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "akamai",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "Origin Server Connectivity Issues with Elevated Errors in APAC Region",
  "retryAfterSec": null,
  "incident": {
    "title": "Origin Server Connectivity Issues with Elevated Errors in APAC Region",
    "url": "https://www.akamaistatus.com/incidents/fmpdhlpkr4jp"
  },
  "probe": null
}

Questions

Is Akamai down right now?
Partly. As of 2026-10-10 07:17 UTC, Akamai is having issues, with an open incident: "Origin Server Connectivity Issues with Elevated Errors in APAC Region". This page reads the status again every 3 minutes.
How long do Akamai outages usually last?
Of the 5 incidents Akamai reported in the last 90 days, half were resolved within 1 h 15 min and nine in ten within 8 days; the longest took 8 days. These are the provider's own start and end times.
Where does this status come from?
From Akamai's own status page API at https://www.akamaistatus.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Akamai's words.
Can I get an alert when Akamai goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Akamai reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/akamai/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Akamai status?
Fetch https://upbutler.com/status/akamai/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"akamai"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Akamai's?
Add "akamai" to the dependencies of your UpButler workspace. When one of your monitors fails while Akamai has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Akamai. Status and incident text belong to Akamai and are read from their public status source; the probe result is UpButler's own measurement.