Downrightnow
// Incident Post-MortemDRN-E222ADAD

Diablo 4 outage on May 25, 2026

Major severityResolved0 minGaming
Started · UTC
May 25, 02:36 PM
2h ago
Resolved · UTC
May 25, 02:36 PM
2h ago
Duration
0 min
End-to-end
Peak confidence
100.00
38 snapshots
// User impact

Diablo 4 users likely saw failed connections, degraded availability, or session instability for this gaming service. The incident reached Major severity and lasted 0 min. The stored report window does not show a preserved user-report spike.

// What happened

Diablo 4 appears to be operating normally based on current signals. DNS is no recent DNS check, user reports are quiet.

Cached · Mon, May 25, 2026, 03:10 PM UTC · scope: this incident

// Timeline
  1. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Major confidence crossed the incident threshold for Diablo 4.

  3. Marked resolved

    The incident was closed after 0 min of observed impact.

  4. Status changed to Major Outage

    The stored readout moved to Major Outage with confidence 40.00.

  5. Status changed to Recovering

    The stored readout moved to Recovering with confidence 30.00.

  6. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

// Signals by source0 sources

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

// Aggregate evidence

Confidence scoring

100.00

The incident reached 100.00 peak confidence across 38 stored status snapshots.

User reports

0 / 15m

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

Status samples

9 affected

9 snapshots in the window showed degraded, recovering, or major-outage state before recovery.

Recovery signal

Resolved

Recovery was recorded at Mon, May 25, 2026, 02:36 PM UTC.