Vercel incident
Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions
Resolved after 4 hours 43 minutes, affecting Functions, on April 2, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
- 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.
- resolved Apr 02, 2026, 06:53 PM UTC
This incident has been resolved.
Your product runs on more than Vercel
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services