Summary
This incident has been resolved.
Impact
minor
Timeline
[investigating] We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are currently investigating this issue and will provide additional updates as they become available.
via statuspage[investigating] We are seeing signs of recovery and the affected build queue has started to drain. Some customers may continue to experience delayed build starts or builds stuck in an initializing state while recovery continues. We will provide additional updates as they become available.
via statuspage[monitoring] Build queues have returned to normal levels, and build processing should be restored. We are monitoring to ensure the service remains stable. We will provide additional updates as they become available.
via statuspage[monitoring] The issue affecting build queue processing has been resolved, and build queues have returned to normal. Builds are now processing as expected. We are continuing our internal root cause analysis.
via statuspage[resolved] This incident has been resolved.
via statuspageLessons Learned
⚠Vercel has experienced 45 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to api, capacity have occurred 773 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Capacity Issue, API Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Elevated error rates for Opus 4.5
Anthropic · Jul 20, 2026
Elevated errors for GitHub-dependent ChatGPT and Codex workflows
OpenAI · Jul 20, 2026
Incident with GitHub Actions
GitHub · Jul 19, 2026
Elevated errors affecting ChatGPT
OpenAI · Jul 19, 2026
Networking in BLR1
DigitalOcean · Jul 19, 2026