Live / UCSB / Incident
UCSB: 504 Gateway Time-Out message on SSO Sites
UCSB · ucsb.eduCritical outageResolved2026-11-09 17:17 UTC
Public — what happened
Summary
UCSB said that applications requiring single sign-on were showing a 504 Gateway Time-Out error, starting at 14:12 UTC on 2026-10-29. The university said its identity engineering team was working to restore service and that a campus-wide message about the outage had been sent. By 15:40 UTC the same day, UCSB reported that logins were succeeding on critical services such as ServiceNow, Kronos and UCPath, and it suggested clearing the browser cache, using a private window, or restarting the browser for anyone still affected. The incident was marked resolved on 2026-11-09 at 17:17, and no cause was given in the text provided.
Affected
SSO
Timeline
- Started — 2026-10-29 14:12 UTC
- Investigating — 2026-10-29 14:12 UTC (2 updates)
- Monitoring — 2026-10-29 15:40 UTC
- Resolved — 2026-11-09 17:17 UTC · 11 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach UCSB against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for UCSB: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the UCSB report →
More from UCSB
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.