Major incident

UCSB: Timekeeping service (Kronos/UKG) 503 Error

Affected: Electronic Timekeeping (Kronos)

Current status of UCSB: Partial outage — live UCSB status

Timeline

1. Oct 8, 2026, 18:35 UTC
   investigating
   We are currently investigating an issue affecting access to the Timekeeping service (Kronos/UKG). Users trying to log in are encountering a 503 Service Temporarily Unavailable error. Our technical teams are actively looking into the cause to restore access as quickly as possible. We will post further updates as soon as more information becomes available.
2. Oct 8, 2026, 19:05 UTC
   monitoring
   Login access to the Timekeeping service (Kronos/UKG) has been restored. We are currently monitoring system performance to ensure stability. If you continue to experience a 503 error, please try clearing your browser cache and cookies or restarting your browser. We will provide another update once we confirm full service stability.
3. Oct 8, 2026, 22:38 UTC
   resolved
   The issue affecting access to the Timekeeping service (Kronos/UKG) has been fully resolved, and systems are operating normally. Our vendor confirmed that the login disruptions were caused by a temporary Google Cloud storage outage affecting authentication services between 11:20 AM and 12:00 PM PDT (2:20 PM – 3:00 PM ET). Service has been fully restored, and system stability has been re-verified. If you still experience issues, please clear your browser cache and cookies or restart your browser.

Updates as published by UCSB (original).