Vercel Multiple Outages April: Deployments, Webhooks, Support
What happened
Vercel experienced a series of platform incidents between March 31 and April 1 that disrupted core development workflows. The first incident on March 31 prevented users from submitting support cases for approximately 13 minutes. Later that day, deployments began failing with "invalid request" errors, requiring teams to manually redeploy affected builds. A third incident on April 1 caused deployment failures specifically for projects using integrations and introduced significant delays in webhook delivery, lasting over 90 minutes before resolution.
Business impact
Background
Vercel hosts websites and applications for major enterprise customers who depend on reliable deployment infrastructure for continuous delivery. Webhook delays are particularly problematic for e-commerce and SaaS platforms that use them for real-time integrations with payment processors, CRMs, and analytics tools. The clustering of these incidents within 48 hours suggests potential underlying infrastructure stress.
What this means for your team
What to watch
Monitor Vercel's incident frequency and duration patterns, particularly for deployment and integration-related issues. Teams should track whether these incidents become more frequent, which could indicate scaling challenges with Vercel's infrastructure.
Sources
-
Incident with Issues and Webhooks
GitHub Status
-
Durable Object and D1 Analytics Delayed
Cloudflare Status
-
Incorrect rejection of 400 errors for AI Gateway
Cloudflare Status
-
Disruption with GitHub's code search
GitHub Status
-
Delayed Credit Usage Updates
Netlify Status
-
Environment Variables Issues
Netlify Status
-
Elevated Build Errors for Secure Compute/Static IPs Projects
Vercel Status
-
Load Balancing health monitoring impacted
Cloudflare Status
-
Elevated Errors Creating Deployments
Vercel Status
-
Elevated errors creating deployments with integrations and increased delays in delivering webhooks
Vercel Status