Linode (Akamai): SLA evidence report
Linode (Akamai): SLA evidence report
- Measured downtime
- 22h 29m
- Across 3 outages in this window.
- Window
- 2026-09-05 to 2026-10-05
- UTC, 30 days.
Sep 21, 2026, 4:59 AM UTC to Sep 22, 2026, 2:40 AM UTC
Multiple regions: South America, Australia
21h 40mmeasured in this window
Linode (Akamai)'s claim at the time: Said operational at first, then acknowledged a problem
Sep 7, 2026, 11:58 AM UTC to Sep 7, 2026, 12:08 PM UTC
Single region: Europe
9.8mmeasured in this window
Linode (Akamai)'s claim at the time: Acknowledged a problem for the outage
Sep 7, 2026, 10:48 AM UTC to Sep 7, 2026, 11:27 AM UTC
Multiple regions: Europe, US-East, US-West
38.9mmeasured in this window
Linode (Akamai)'s claim at the time: Said operational at first, then acknowledged a problem
What we probed
Methodology
Every outage above is a period our probes measured Linode (Akamai) as down from enough of the regions we check it from to count as a real outage, not a single unreliable reading (see how we tell the difference). Measured downtime is the wall-clock time inside the window an outage's regions were failing; regions failing together still count as one outage, not one per region.
Linode (Akamai)'s claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from what we measured. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.
This is one external observation from RealUptime's own regions, not Linode (Akamai)'s own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we probe. The credit estimate above is a starting point for a conversation with Linode (Akamai), not a legal determination, and RealUptime is not counsel.