Akamai outage on August 14 — 10h 30m disruption
Aug 14, 06:51 AM → Aug 14, 05:22 PM · 10h 30m · medium
On August 14, 2026, Akamai experienced a service disruption. This incident was detected through user reports indicating issues with the service. The disruption was resolved on August 14, 2026, at 17:22 UTC.
Impact
During the incident, users reported a medium-severity disruption to Akamai services. A total of 164 user reports were received, with a peak of 4 reports within a 15-minute period. The primary issue reported by users was 'Website down'. No specific top impacted regions were recorded during this event.
Top reported issues
- Website down164
Incident timeline
- Aug 14, 06:51 AM
PulseWatch detected elevated report volume (medium severity)
- Aug 14, 07:00 AM
Peak of 4 reports in 15 minutes (baseline 1.3)
- Aug 14, 12:22 PM
Status updated: possible issue
- Aug 14, 12:28 PM
Status updated: possible issue
- Aug 14, 12:38 PM
Status updated: possible issue
- Aug 14, 12:42 PM
Status updated: possible issue
- Aug 14, 12:48 PM
Status updated: possible issue
- Aug 14, 12:51 PM
Status updated: possible issue
- Aug 14, 12:57 PM
Status updated: possible issue
- Aug 14, 01:08 PM
Status updated: possible issue
- Aug 14, 01:12 PM
Status updated: possible issue
- Aug 14, 01:18 PM
Status updated: possible issue
- Aug 14, 01:22 PM
Status updated: possible issue
- Aug 14, 01:28 PM
Status updated: possible issue
- Aug 14, 01:38 PM
Status updated: possible issue
- Aug 14, 01:42 PM
Status updated: possible issue
- Aug 14, 01:48 PM
Status updated: possible issue
- Aug 14, 01:52 PM
Status updated: possible issue
- Aug 14, 01:59 PM
Status updated: possible issue
- Aug 14, 02:08 PM
Status updated: possible issue
- Aug 14, 02:12 PM
Status updated: possible issue
- Aug 14, 02:18 PM
Status updated: possible issue
- Aug 14, 02:22 PM
Status updated: possible issue
- Aug 14, 02:27 PM
Status updated: possible issue
- Aug 14, 02:38 PM
Status updated: possible issue
- Aug 14, 02:42 PM
Status updated: possible issue
- Aug 14, 02:48 PM
Status updated: possible issue
- Aug 14, 02:52 PM
Status updated: possible issue
- Aug 14, 02:57 PM
Status updated: possible issue
- Aug 14, 03:08 PM
Status updated: possible issue
- Aug 14, 03:12 PM
Status updated: possible issue
- Aug 14, 03:18 PM
Status updated: possible issue
- Aug 14, 03:22 PM
Status updated: possible issue
- Aug 14, 03:28 PM
Status updated: possible issue
- Aug 14, 03:38 PM
Status updated: possible issue
- Aug 14, 03:42 PM
Status updated: possible issue
- Aug 14, 03:48 PM
Status updated: possible issue
- Aug 14, 03:52 PM
Status updated: possible issue
- Aug 14, 03:57 PM
Status updated: possible issue
- Aug 14, 04:08 PM
Status updated: possible issue
- Aug 14, 04:12 PM
Status updated: possible issue
- Aug 14, 04:18 PM
Status updated: possible issue
- Aug 14, 04:23 PM
Status updated: possible issue
- Aug 14, 04:31 PM
Status updated: possible issue
- Aug 14, 04:38 PM
Status updated: possible issue
- Aug 14, 04:42 PM
Status updated: possible issue
- Aug 14, 04:48 PM
Status updated: possible issue
- Aug 14, 04:52 PM
Status updated: possible issue
- Aug 14, 04:57 PM
Status updated: possible issue
- Aug 14, 05:08 PM
Status updated: possible issue
- Aug 14, 05:12 PM
Status updated: possible issue
- Aug 14, 05:22 PM
Report volume returned to baseline — incident resolved
Official updates
- Aug 14, 06:51 AM
Akamai status page acknowledged the incident.
View official source