v0 (Vercel) · 90d ago
Errors accessing teams that require 2FA
ResolvedYes — v0 had a problem on July 15, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved.”
Timeline
Started: 7/15/2026, 11:04:43 PM
Last update: 7/15/2026, 11:34:54 PM
Resolved: 7/15/2026, 11:34:54 PM
Affected: fk66q26xp7hh, rsp3h37vv009, rxynwj392p81
Updates
resolved
This incident has been resolved.
7/15/2026, 11:34:54 PM
monitoring
A fix has been implemented and services have recovered. We are continuing to monitor to ensure that the services remain stable. We will provide additional updates as they become available.
7/15/2026, 11:16:23 PM
identified
We have identified an increase in erroneous 2FA (two-factor authentication) challenges and errors when accessing the Vercel dashboard and multiple API services for teams that require 2FA. We will share more information once we have it.
7/15/2026, 11:04:43 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