Vercel incident: Elevated errors across multiple services in IAD1 (Washington, D.C., USA)

1. resolvedMay 8, 2026, 06:39 UTC

   We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Vercel's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• ReadMe: Issues Creating New ChangelogsCritical · May 7, 2026, 23:43 UTC
• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Convex: Intermittent Impact from AWS OutageMajor · May 8, 2026, 00:16 UTC
• Cursor: Investigating Service DegradationMajor · May 8, 2026, 00:43 UTC
• Supabase: Network connectivity in us-east-1-az4Major · May 8, 2026, 00:50 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Twilio: Voice Call Audio Quality Degradation Between Twilio Phone Numbers and Multiple Networks in United KingdomMinor · May 2, 2026, 18:00 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Short Codes to Google Voice United StatesMinor · May 4, 2026, 20:40 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC

How often does Vercel have incidents?

Vercel reported 24 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 59 min. See Vercel's uptime and incident history