v0 (Vercel) · 89d ago
GitHub-linked deployments and authentication affected
ResolvedYes — v0 had a problem on July 16, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved.”
Timeline
Started: 7/16/2026, 11:09:29 PM
Last update: 7/17/2026, 12:42:10 AM
Resolved: 7/17/2026, 12:42:10 AM
Affected: fk66q26xp7hh, 7ckq6xr6nsbv, hpqj1ys9gr78
Updates
resolved
This incident has been resolved.
7/17/2026, 12:42:10 AM
monitoring
Deployments for projects linked to GitHub repositories are recovering. 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. GitHub login, signup, and account connections are recovered.
7/17/2026, 12:07:15 AM
identified
We've identified an issue affecting deployments for projects linked to GitHub repositories, as well as GitHub login, signup, and account connections. CLI deployments and other sign-in methods are unaffected. We will share updates as they become available.
7/16/2026, 11:39:29 PM
investigating
We are investigating elevated error rates for users logging in to Vercel using their GitHub account and connecting their GitHub accounts to Vercel. Login with email or other sign-in methods is unaffected.
7/16/2026, 11:09:29 PM
More v0 (Vercel) incidents
- Increased build and deployment failures — resolved, 1d ago
- Delays in Drains, Observability, and Workflow in Washington (iad1) — resolved, 4d ago
- Vercel Auth login failures for pages with Deployment Protection enabled — resolved, 7d ago
- Elevated Sandbox error rates in Paris (cdg1) — resolved, 7d ago
- Build failures and 500 errors for functions using Edge runtime — resolved, 15d ago
- Deployment stuck in initializing state — resolved, 25d ago