Is Akamai down in the US?
Vendor lists an old incident, not shown as liveWhat Akamai reports
Akamai still lists an incident opened on 2026-10-30 with no update since 2026-11-02; we do not show it as live.
As of the last successful poll, 2026-11-05 22:16 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin the US, measured from Ashburn, San Jose, and Chicago
All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked Akamai at Nov 5, 2026, 10:19 PM UTC.
Over the last 24 hours we completed 328 checks from Ashburn, San Jose, and Chicago and 328 answered cleanly, 100.00% availability.
Of the 7 other regions we check Akamai from, all 7 read checks passing right now.
Email me when Akamai reports an incident on its status page, and again when it reports it resolved.
What our Ashburn, San Jose, and Chicago probes measured
Last checked Nov 5, 2026, 10:19 PM UTC.
Akamai from Ashburn, San Jose, and Chicago over the last 30 days
Over the last 30 days, Akamai answered our Chicago probe in 301 ms on average, and 1 check in 20 took longer than 641 ms.
Over the last 30 days, Akamai answered our Ashburn probe in 386 ms on average, and 1 check in 20 took longer than 791 ms.
Over the last 30 days, Akamai answered our San Jose probe in 456 ms on average, and 1 check in 20 took longer than 915 ms.
Ranked by average response time across the 10 cities we check Akamai from, Chicago 3rd, Ashburn 5th, San Jose 6th; Frankfurt was fastest at 225 ms and São Paulo slowest at 745 ms.
From Ashburn, San Jose, and Chicago we ran 10,649 checks of Akamai in 30 days, and 10,648 answered cleanly: 99.99% availability.
1 of the 30 days had at least one failed check. The weakest was Oct 26 (UTC), at 99.72% across 358 checks.
In Ashburn local time (EST), Akamai was slowest around 3 PM, at 584 ms on average over the last 14 days, and quickest around 1 PM, at 339 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 299 | 100.00% | 810 ms |
| Wed, Nov 4 | 327 | 100.00% | 688 ms |
| Tue, Nov 3 | 322 | 100.00% | 754 ms |
| Mon, Nov 2 | 345 | 100.00% | 677 ms |
| Sun, Nov 1 | 360 | 100.00% | 516 ms |
| Sat, Oct 31 | 359 | 100.00% | 374 ms |
| Fri, Oct 30 | 359 | 100.00% | 509 ms |
| Thu, Oct 29 | 360 | 100.00% | 513 ms |
| Wed, Oct 28 | 358 | 100.00% | 510 ms |
| Tue, Oct 27 | 363 | 100.00% | 404 ms |
| Mon, Oct 26 | 358 | 99.72% | 411 ms |
| Sun, Oct 25 | 363 | 100.00% | 436 ms |
| Sat, Oct 24 | 360 | 100.00% | 351 ms |
| Fri, Oct 23 | 360 | 100.00% | 351 ms |
Akamai outages measured from the US
Our Ashburn, San Jose, and Chicago probes measured no confirmed Akamai outage in the last 90 days.
How the other regions read right now
Of the 7 other regions we check Akamai from, all 7 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 101 checks |
| Tokyo | Checks passing | 100.00% of 62 checks |
| Toronto | Checks passing | 100.00% of 72 checks |
| London | Checks passing | 100.00% of 72 checks |
| Singapore | Checks passing | 100.00% of 72 checks |
| Sydney | Checks passing | 100.00% of 72 checks |
| São Paulo | Checks passing | 100.00% of 72 checks |
Other countries we check Akamai from
How we measured this
The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against Akamai's public endpoints. They are not user reports, and they are not Akamai's own status page.
See Akamai's full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter