Vercel incident: Support cases cannot be submitted

1. resolvedMay 18, 2026, 15:41 UTC

   The incident is resolved and support cases can be submitted again.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 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
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Twilio: SMS Delivery Failures between Twilio Phone Numbers and AT&T in MexicoMinor · May 14, 2026, 20:50 UTC
• Twilio: Subset of AU Sender ID Registration Submissions Directly Transitioning to REJECTEDMinor · May 15, 2026, 20:51 UTC
• Grafana Cloud: Grafana K6 metrics processing and test runs degradationMinor · May 18, 2026, 08:24 UTC
• Snyk: Service Degradation on US-01 (app.snyk.io)Minor · May 18, 2026, 12:12 UTC
• ClickHouse Cloud: GCP us-east1 capacity constraints impacting cluster operationsMinor · May 18, 2026, 12:31 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