Linode outage on March 24, 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
Incident detected
Minor confidence crossed the incident threshold for Service Issue - New Linode Creation.
Marked resolved
The incident was closed after 45 min of observed impact.
No per-source signal payloads were preserved in this incident's snapshot window.
Confidence scoring
45.00The incident reached 45.00 peak confidence across available 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 Tue, Mar 24, 2026, 10:10 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.