Harness incident
Degraded Performance for SCIM users during login.
Harness experienced a minor incident on March 19, 2026 affecting Management Console, lasting 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 19, 2026, 04:14 PM UTC
The issue has been identified and a fix is in place.
- monitoring Mar 19, 2026, 04:42 PM UTC
The issue has been identified and a fix is in place. (Note: It is still in a degraded state)
- monitoring Mar 19, 2026, 04:42 PM UTC
The issue has been identified and a fix is in place.
- monitoring Mar 19, 2026, 04:59 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 19, 2026, 04:59 PM UTC
This incident has been resolved.
- postmortem Apr 02, 2026, 12:45 AM UTC
## Summary Between **05:48 PM UTC on March 18** and **04:58 PM UTC on March 19**, two customers using [app.split.io](http://app.split.io/) with **SAML authentication using SCIM** experienced login failures. The issue was limited to customers with specific identity provisioning configurations. ## Root Cause A service update was deployed to a login-related component that changed internal request handling behavior. This caused authentication workflows for SAML-configured customers with identity provisioning enabled to fail during login processing. ## Impact * 2 customers using SAML authentication **with SCIM provisioning enabled** were unable to log in to [app.split.io](http://app.split.io/). * Customers using SAML authentication without SCIM were not affected and could log in normally. * Username and password login was unaffected. * SDKs, feature flags, and experiments continued functioning normally. * No data loss occurred. ## Remediation * Rolled back the service update that introduced the issue. * Restored SAML login for affected customers. ## Action Items To prevent such issues from happening again, here are the action items. * **Improve detection capability**: Introduced a high-priority alert to detect authentication failures sooner, enabling faster response if similar issues occur in the future. * **Reduce legacy surface area**: Continue guiding remaining customers toward the Harness Platform, where authentication flows are unified and improvements can be delivered more consistently over time.