Vercel incident
Elevated errors (SIGSEGV) for Vercel Functions running Node.js 20 in cle1 and dub1 regions
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.
Looking to track Vercel downtime and outages?
Pingoru polls Vercel's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Vercel reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Vercel alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required