Live  /  UCSB  /  Incident

UCSB: Timekeeping service (Kronos/UKG) 503 Error

UCSB · ucsb.eduMajor incidentResolved2026-10-08 22:38 UTC
Public — what happened

Summary

UCSB reported a major problem with its Timekeeping service (Kronos/UKG) starting at 18:35 UTC on 2026-10-08, when people attempting to sign in were shown a 503 error saying the service was temporarily unavailable. By 19:05 UTC the university said sign-in was working again and it was watching the system for stability, suggesting anyone still seeing the error clear their browser cache and cookies or restart their browser. UCSB did not say what caused the issue, and it marked the incident resolved at 22:38.

Affected

Electronic Timekeeping (Kronos)

As listed on UCSB’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the UCSB status & history page.

Related: UCSB status & history. SquidGrid is not affiliated with UCSB.