Vercel incident

Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions

Minor Resolved View vendor source →

Vercel experienced a minor incident on April 2, 2026 affecting Functions, lasting 4h 43m. The incident has been resolved; the full update timeline is below.

Started
Apr 02, 2026, 02:10 PM UTC
Resolved
Apr 02, 2026, 06:53 PM UTC
Duration
4h 43m
Detected by Pingoru
Apr 02, 2026, 02:10 PM UTC

Affected components

Functions

Update timeline

  1. investigating Apr 02, 2026, 02:10 PM UTC

    We are currently investigating increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV. We recommend redeploying affected Vercel Functions or upgrading them to either Node.js 22 or 24.

  2. investigating Apr 02, 2026, 04:13 PM UTC

    We are continuing to investigate increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV in Vercel's cle1 and dub1 regions. Other regions are unaffected. We recommend redeploying affected Vercel Functions or upgrading them to either Node js 22 or 24.

  3. monitoring Apr 02, 2026, 06:09 PM UTC

    The root cause has been identified, a fix has been rolled out, and we are actively monitoring. Newly deployed Vercel Functions on Node.js 20 in cle1 and dub1 no longer terminate with SIGSEGV. We recommend redeploying affected Vercel Functions if you are still seeing issues.

  4. resolved Apr 02, 2026, 06:53 PM UTC

    This incident has been resolved.