Isitreallydown?
// Incident Post-MortemDRN-08DA4912

Vercel outage on May 9, 2026

Minor severityResolved45 minCloud
Started · UTC
May 09, 04:45 AM
3d ago
Resolved · UTC
May 09, 05:30 AM
3d ago
Duration
45 min
End-to-end
Peak confidence
25.00
17 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. Status changed to Operational

    The stored readout moved to Operational with confidence 55.00.

  2. Incident detected

    Minor confidence crossed the incident threshold for Vercel Queues, and Vercel Workflow runs were delayed.

  3. Marked resolved

    The incident was closed after 45 min of observed impact.

  4. Peak confidence reached

    Confidence peaked at 60.00 while the service was marked Operational.

// Signals by source1 sources
  • Official status

    Www.Vercel-Status.Com reported an open incident — Vercel Queues, and Vercel Workflow runs were delayed (Queues, Workflow) · impact: minor

    04:57 AM UTC
// Aggregate evidence

Confidence scoring

25.00

The incident reached 25.00 peak confidence across 17 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 09, 2026, 05:30 AM 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.