Akamai outage on August 13 — 7h 34m disruption
Aug 13, 10:43 PM → Aug 14, 06:18 AM · 7h 34m · high
On August 13, 2026, Akamai experienced a service disruption. The incident began at 22:43 UTC and was resolved on August 14, 2026, at 06:18 UTC.
Impact
Users reported issues with Akamai services, primarily experiencing website downtime. The disruption was detected via user reports, with a total of 124 reports received during the incident, peaking at 4 reports within a 15-minute window. No specific regional impact was recorded.
Top reported issues
- Website down124
Incident timeline
- Aug 13, 10:43 PM
PulseWatch detected elevated report volume (high severity)
- Aug 13, 10:45 PM
Peak of 4 reports in 15 minutes (baseline 1.3)
- Aug 14, 12:48 AM
Status updated: possible issue
- Aug 14, 12:53 AM
Status updated: possible issue
- Aug 14, 12:58 AM
Status updated: possible issue
- Aug 14, 01:03 AM
Status updated: possible issue
- Aug 14, 01:08 AM
Status updated: possible issue
- Aug 14, 01:13 AM
Status updated: possible issue
- Aug 14, 01:18 AM
Status updated: possible issue
- Aug 14, 01:23 AM
Status updated: possible issue
- Aug 14, 01:28 AM
Status updated: possible issue
- Aug 14, 01:33 AM
Status updated: possible issue
- Aug 14, 01:38 AM
Status updated: possible issue
- Aug 14, 01:43 AM
Status updated: possible issue
- Aug 14, 01:48 AM
Status updated: possible issue
- Aug 14, 01:53 AM
Status updated: possible issue
- Aug 14, 01:58 AM
Status updated: possible issue
- Aug 14, 02:03 AM
Status updated: possible issue
- Aug 14, 02:08 AM
Status updated: possible issue
- Aug 14, 02:13 AM
Status updated: possible issue
- Aug 14, 02:18 AM
Status updated: possible issue
- Aug 14, 02:37 AM
Status updated: possible issue
- Aug 14, 02:41 AM
Status updated: possible issue
- Aug 14, 02:51 AM
Status updated: possible issue
- Aug 14, 02:56 AM
Status updated: possible issue
- Aug 14, 03:06 AM
Status updated: possible issue
- Aug 14, 03:11 AM
Status updated: possible issue
- Aug 14, 03:21 AM
Status updated: possible issue
- Aug 14, 03:26 AM
Status updated: possible issue
- Aug 14, 03:36 AM
Status updated: possible issue
- Aug 14, 03:41 AM
Status updated: possible issue
- Aug 14, 03:51 AM
Status updated: possible issue
- Aug 14, 03:56 AM
Status updated: possible issue
- Aug 14, 04:06 AM
Status updated: possible issue
- Aug 14, 04:11 AM
Status updated: possible issue
- Aug 14, 04:22 AM
Status updated: possible issue
- Aug 14, 04:26 AM
Status updated: possible issue
- Aug 14, 04:36 AM
Status updated: possible issue
- Aug 14, 04:41 AM
Status updated: possible issue
- Aug 14, 04:48 AM
Status updated: possible issue
- Aug 14, 04:51 AM
Status updated: possible issue
- Aug 14, 04:56 AM
Status updated: possible issue
- Aug 14, 05:06 AM
Status updated: possible issue
- Aug 14, 05:11 AM
Status updated: possible issue
- Aug 14, 05:21 AM
Status updated: possible issue
- Aug 14, 05:26 AM
Status updated: possible issue
- Aug 14, 05:36 AM
Status updated: possible issue
- Aug 14, 05:41 AM
Status updated: possible issue
- Aug 14, 05:51 AM
Status updated: possible issue
- Aug 14, 05:56 AM
Status updated: major issue
- Aug 14, 06:06 AM
Status updated: major issue
- Aug 14, 06:11 AM
Status updated: major issue
- Aug 14, 06:18 AM
Report volume returned to baseline — incident resolved
Official updates
- Aug 13, 10:43 PM
Akamai status page acknowledged the incident.
View official source