Linode outage on May 8, 2026
Nothing’s wrong that we can see: DNS is resolving normally, there are no regional network anomalies flagged, and Linode’s region health view shows all 16 LINODE regions healthy, but Isitreallydown? does not yet have fresh synthetic probe results (Telemetry confidence: medium). Linode’s official status page is reporting a minor, identified incident titled “Service Issue - GPU and VPU Booting issues,” and they’ve also noted a minor issue affecting US-East (Newark, US) / Linode.com; with problem signals otherwise quiet, there’s no widespread customer impact observed, but workloads depending on GPU/VPU boot flows or that region may see elevated risk.
Cached · Sun, May 10, 2026, 10:41 AM UTC · scope: service signals
Status changed to Operational
The stored readout moved to Operational with confidence 55.00.
Incident detected
Minor confidence crossed the incident threshold for [DirtyFrag] Linux Privilege Escalation Vulnerability.
Marked resolved
The incident was closed after 45 min of observed impact.
Peak confidence reached
Confidence peaked at 60.00 while the service was marked Operational.
- Official status
Status.Linode.Com reported an open incident — [DirtyFrag] Linux Privilege Escalation Vulnerability (US-East (Newark), Linode.com, US-East (Newark) Block Storage) · impact: none
02:00 PM UTC
Confidence scoring
25.00The incident reached 25.00 peak confidence across 18 stored status snapshots.
User reports
0 / 15mNo elevated user-report volume was preserved in the incident window snapshots.
Status samples
0 affectedThe incident row exists, but the bounded snapshot window does not include affected status samples.
Recovery signal
ResolvedRecovery was recorded at Fri, May 08, 2026, 02:25 PM UTC.
Linode users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.