Is Akamai Down?

No — Akamai is up

Reachable from all 8 checked regions

Average response time: 319ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://www.akamaistatus.com

Akamai uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

204ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 9 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

47ms

DNS 0ms TCP 0ms TLS 2ms TTFB 47ms

bom

393ms

DNS 0ms TCP 2ms TLS 5ms TTFB 392ms

cdg

142ms

DNS 0ms TCP 1ms TLS 3ms TTFB 142ms

dfw

55ms

DNS 0ms TCP 1ms TLS 5ms TTFB 55ms

ewr

79ms

DNS 0ms TCP 4ms TLS 5ms TTFB 79ms

fra

51ms

DNS 0ms TCP 1ms TLS 4ms TTFB 50ms

gru

1714ms

DNS 0ms TCP 131ms TLS 264ms TTFB 1714ms

iad

73ms

DNS 0ms TCP 3ms TLS 4ms TTFB 73ms

What Akamai does

Akamai runs one of the largest content delivery and edge security networks, serving websites, APIs, video and software downloads from servers close to the user. Its platform also covers DNS, web application firewalling, DDoS mitigation through Prolexic, bot management and enterprise access. Banks, retailers, media companies and software vendors put it in front of their origins, so an Akamai fault surfaces as their own site failing.

What an outage looks like

Sites and APIs behind Akamai return errors or time out while origin servers stay healthy, and DNS lookups can fail for domains on Edge DNS. Akamai reports dozens of components separately, so the affected piece is often narrow: Content Purge or Configuration Deployment can fail while Edge Delivery is normal, meaning traffic flows but changes cannot be pushed.

What to do about it

Read www.akamaistatus.com and match the failing component to what you depend on rather than reading the headline. If Content Purge or Configuration Deployment is affected, stale content stays cached and an emergency fix will not take, so plan around the delay instead of retrying. Enterprise Application Access has its own page at eaa-status.akamai.com, which the main page does not cover.

Is it down for everyone, or just you?

If this page says Akamai is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Cloudflare

Fastly

AWS

Bunny.net

Akamai outage FAQ

Akamai says everything is operational but my purge is not working. Why?

Content Purge is its own component, separate from Edge Delivery. Traffic can be served normally while purge requests queue or fail, so the version visitors see stays stale even though nothing is technically down. Check the Content Purge and Configuration Deployment rows specifically, and expect an emergency content fix to be delayed rather than applied.

Does an Akamai outage affect my DNS?

Only if you use Akamai for DNS. Edge DNS is reported as a component separate from delivery, so name resolution can fail for domains on Akamai's nameservers while content delivery is healthy, or the reverse. If lookups are failing, that is a wider failure than a slow site, because every service on the domain is affected including mail.

Can I open a support case during an Akamai incident?

Not necessarily. Akamai reports Case Ticketing, Chat, Email and Telephony as components on the same page, so the channels you would use to report a problem can be affected by the same event. If those rows are degraded, rely on the status page and its updates rather than waiting on a ticket that may not have been created.

Is Enterprise Application Access covered by the main Akamai status page?

It has its own maintenance status page at eaa-status.akamai.com in addition to the Enterprise Application Access rows on the main page. If your users reach internal applications through Akamai rather than a VPN, check both, because a green main page is not evidence that the access layer your staff depend on is healthy.

How we measure this

We request Akamai's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Akamai publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Akamai goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required