Minor impactResolvedCloud

Vercel incident: Elevated Errors Creating New Deployments

Vercel reported this minor-impact incident on its official status page on Jun 1, 2026, 19:21 UTC. It was resolved after 41 min.

Right now Vercel is operational. Live Vercel status →

🔔 Get alerted when Vercel has issuesFree · email alerts · no credit card
Jun 1, 2026, 19:21 UTC
started
Jun 1, 2026, 20:02 UTC
resolved
41 min
duration
Minor
impact

Affected components

  • Builds

Timeline

updates from Vercel's status page ↗
  1. resolvedJun 1, 2026, 20:02 UTC

    This incident has been resolved.

  2. monitoringJun 1, 2026, 19:55 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedJun 1, 2026, 19:50 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingJun 1, 2026, 19:21 UTC

    We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

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.

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

← Previous: Elevated Function Invocation Errors in Stockholm region (ARN1) (May 28, 2026)Next: Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region (Jun 8, 2026) →
Vercel incident on Jun 1, 2026: Elevated Errors Creating New Deployments · APIStatus.watch