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

What to do

• Check whether you use Vercel Functions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 43m it lasted.

  Anything that failed between 2026-04-02 14:10 UTC and 2026-04-02 18:53 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 4

1. investigatingApr 2, 2026, 2: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.

   provider

2. investigatingApr 2, 2026, 4: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.

   provider

3. monitoringApr 2, 2026, 6: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.

   provider

4. resolvedApr 2, 2026, 6:53 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.