Kallidus incident

Page Loading Issue: Learn

Resolved after 23 hours 16 minutes, on August 25, 2026.

postmortem Aug 26, 2026, 01:09 PM UTC

Service disruption: Learn access issue — 25 August 2026 Summary: Between approximately 12:00 and 17:00 on 25 August 2026, a subset of customers were unable to use Learn after logging in — users authenticated successfully but were then stuck on a loading screen. Other parts of the Kallidus platform, including Learn admin, Manager users, Reports and Perform, were unaffected. Status: Resolved. Service was restored at 17:00, and affected users have been able to log in and use Learn normally since. Cause: A configuration change made at approximately 12:00 increased the size of the authentication data issued at login. For a subset of customers, this pushed that data over a size limit enforced by the browser, causing it to be silently discarded — which left affected users stuck in a login loop with no visible error. Remediation: We identified and reverted the change, and are implementing additional safeguards to detect this class of issue before it reaches customers in future. We apologise for the disruption this caused.

Started
Aug 25, 2026, 01:53 PM UTC
Resolved
Aug 26, 2026, 01:09 PM UTC
Duration
23h 16m
Detected by Pingoru
Aug 25, 2026, 01:53 PM UTC

Update timeline

  1. postmortem Aug 26, 2026, 01:09 PM UTC

    Service disruption: Learn access issue — 25 August 2026 Summary: Between approximately 12:00 and 17:00 on 25 August 2026, a subset of customers were unable to use Learn after logging in — users authenticated successfully but were then stuck on a loading screen. Other parts of the Kallidus platform, including Learn admin, Manager users, Reports and Perform, were unaffected. Status: Resolved. Service was restored at 17:00, and affected users have been able to log in and use Learn normally since. Cause: A configuration change made at approximately 12:00 increased the size of the authentication data issued at login. For a subset of customers, this pushed that data over a size limit enforced by the browser, causing it to be silently discarded — which left affected users stuck in a login loop with no visible error. Remediation: We identified and reverted the change, and are implementing additional safeguards to detect this class of issue before it reaches customers in future. We apologise for the disruption this caused.

Your product runs on more than Kallidus

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →