Downrightnow
// Incident Post-MortemDRN-F0247B3D

Linode outage on May 16, 2026

Minor severityResolved33 minCloud
Started · UTC
May 16, 12:42 AM
7d ago
Resolved · UTC
May 16, 01:15 AM
7d ago
Duration
33 min
End-to-end
Peak confidence
45.00
15 snapshots
// User impact

Linode users likely saw failed connections, degraded availability, or session instability for this Cloud service. The incident reached Minor severity and lasted 33 min. The stored report window does not show a preserved user-report spike.

// What happened

Linode's official status page is reporting minor affecting Service Issue - GPU and VPU Booting issues. Official impact is region-scoped to AWS ap-northeast-2 (Seoul, South Korea). DNS is no recent DNS check, user reports are quiet. Current signals suggest this may have broader impact.

Cached · Sat, May 23, 2026, 01:49 AM UTC · scope: service signals

// Timeline

  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Linode: emerging Service Issue - [Linodes] - [All Regions].

  3. Marked resolved

    The incident was closed after 33 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 55.00 while the service was marked Operational.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

45.00

The incident reached 45.00 peak confidence across 15 stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Sat, May 16, 2026, 01:15 AM UTC.