Vercel incident: Deployment stuck in initializing state

Affected components

• Builds

1. resolvedSep 18, 2026, 22:31 UTC

   This incident has been resolved.

2. monitoringSep 18, 2026, 22:14 UTC

   We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.

3. investigatingSep 18, 2026, 21:36 UTC

   We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.

What APIStatus.watch saw

• Sep 18, 2026, 21:25 UTCdegraded → operational
• Sep 18, 2026, 21:40 UTCoperational → degraded
• Sep 18, 2026, 22:35 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Cursor: Investigating service degradation — Grok BotMajor · Sep 18, 2026, 17:19 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Notion: Some connected content results unavailable in Notion AIMinor · Sep 17, 2026, 14:07 UTC
• Snyk: Snyk Daily Recurring Tests DelayedMinor · Sep 18, 2026, 06:40 UTC
• Resend: Degraded performanceMinor · Sep 18, 2026, 18:26 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