Vercel Status · History · Incident #5582
RESOLVEDSAML Single Sign-On (SSO) errors
Major · Started Jul 16, 2026 · 8:39 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Vercel Status · History · Incident #5582
RESOLVEDMajor · Started Jul 16, 2026 · 8:39 AM
Duration
2h 5m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Jul 16, 2026 · 8:39 AM
Resolved
Jul 16, 2026 · 10:45 AM
Duration
2h 5m
Severity
Major
Event timeline
Investigating
Jul 16 · 8:39 AM VercelWe 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.
Monitoring
Jul 16 · 10:23 AM VercelThe 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.
Resolved
Jul 16 · 10:45 AM VercelThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.