v0 (Vercel) · 89d ago
SAML Single Sign-On (SSO) errors
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, 8:39:35 AM
Last update: 7/16/2026, 10:45:23 AM
Resolved: 7/16/2026, 10:45:23 AM
Affected: w5nffyn79vx9
Updates
resolved
This incident has been resolved.
7/16/2026, 10:45:23 AM
monitoring
The root cause of the SAML Single Sign-On (SSO) errors has been identified and a fix has been implemented. We are seeing error rates decrease. Users should be able to login with SAML/SSO or access their SSO-protected teams through the Vercel dashboard and CLI again. We are continuing to monitor.
7/16/2026, 10:23:48 AM
investigating
We are investigating SAML Single Sign-On (SSO) errors, leading to inability to login using SAML/SSO or access SSO-protected teams through the Vercel dashboard and CLI.
7/16/2026, 8:39:35 AM
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