Live / Akamai / Incident
Akamai: Media Services Live 4 (MSL4) Issues
Akamai · akamai.comMinor incidentResolved2026-08-26 10:18 UTC
Public — what happened
Summary
Akamai reported a problem with its Media Services Live 4 product beginning at 16:52 UTC on August 25, 2026, in which live streams were returning 502 bad gateway errors. The company said at 18:13 UTC that it had found the cause, though it did not describe it publicly, and that a fix was underway. Akamai said the fix took effect at 18:15 UTC that day, and after a period of monitoring it marked the incident resolved on August 26 at 10:16 UTC. An incident summary report was made available to customers and partners through the Akamai Community site.
Affected
Edge Delivery
Timeline
- Started — 2026-08-25 16:52 UTC
- Investigating — 2026-08-25 16:52 UTC (3 updates)
- Identified — 2026-08-25 18:13 UTC
- Monitoring — 2026-08-25 18:27 UTC
- Postmortem — 2026-08-26 10:18 UTC
- Resolved — 2026-08-26 10:16 UTC · 17h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Akamai against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Akamai: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Akamai report →
More from Akamai