Isitreallydown?
// Incident Post-MortemDRN-59A70318

Vercel outage on April 2, 2026

Minor severityResolved45 minCloud
Started · UTC
Apr 02, 06:53 PM
40d ago
Resolved · UTC
Apr 02, 07:38 PM
40d ago
Duration
45 min
End-to-end
Peak confidence
45.00
0 snapshots
// What happened

Vercel appears to be operating normally based on current signals. Isitreallydown?'s synthetic checks are not yet measured, DNS is resolving normally, user reports are quiet.

Cached · Sun, May 10, 2026, 04:07 AM UTC · scope: service signals

// Timeline
  1. Incident detected

    Minor confidence crossed the incident threshold for Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// 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 available 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 Thu, Apr 02, 2026, 07:38 PM UTC.

// User impact

Vercel 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.