Linode (Akamai): SLA evidence report
Linode (Akamai): SLA evidence report
We hold no probe record for Linode (Akamai): we read its status page, so the only incident record here is what Linode (Akamai) declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Linode (Akamai) declared
- 6
- On its own status page, in this window.
- Window
- 2026-09-22 to 2026-10-22
- UTC, 30 days.
Dec 3, 2025, 3:15 PM UTC to Oct 8, 2026, 9:26 PM UTC
Service Issue - GPU and VPU Booting issues, impact minor
This incident started before the report window shown above.
Sep 21, 2026, 5:13 PM UTC to Sep 23, 2026, 3:26 AM UTC
Emerging Service Issue - Cloud Manager and API, impact minor
This incident started before the report window shown above.
Sep 25, 2026, 3:09 PM UTC to Sep 25, 2026, 4:21 PM UTC
Service Issue - Cloud Manager and API, impact minor
Oct 2, 2026, 4:01 PM UTC to Oct 2, 2026, 8:17 PM UTC
Service Issue - Object Storage - US-Southeast (Atlanta), impact minor
Oct 9, 2026, 3:43 AM UTC to Oct 13, 2026, 8:03 AM UTC
Service Issue - Cloud Manager and API, impact minor
Oct 20, 2026, 12:29 PM UTC to Oct 20, 2026, 9:42 PM UTC
Issue in creating new LKE Enterprise cluster across regions, impact minor
Methodology
These incidents come from Linode (Akamai)'s own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Linode (Akamai) owes, if any, is decided under its own SLA.