SignalFx US0 incident

Customers are not able login using Splunk Cloud (SCS) unified identify login page

Critical Resolved View vendor source →

SignalFx US0 experienced a critical incident on April 17, 2026 affecting SSO OIDC Endpoint, lasting 9h 16m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2026, 08:30 AM UTC
Resolved
Apr 17, 2026, 05:46 PM UTC
Duration
9h 16m
Detected by Pingoru
Apr 17, 2026, 08:30 AM UTC

Affected components

SSO OIDC Endpoint

Update timeline

  1. investigating Apr 17, 2026, 11:48 AM UTC

    Customers are unable to login into Splunk Observability using Splunk Cloud (SCS) unified identify login page. Customers are seeing an internal server error HTTP 500 during login. We are actively investigating this incident.

  2. investigating Apr 17, 2026, 12:18 PM UTC

    Customers are unable to login into Splunk Observability using Splunk Cloud (SCS) unified identify login page. Customers are seeing an internal server error HTTP 500 during login. We are actively investigating this incident.

  3. identified Apr 17, 2026, 12:31 PM UTC

    We have identified the issue and are working on identifying a correct mitigation. Customers will still experience login failures with unified identity in this realm. We will share another update as soon as more information is available.

  4. identified Apr 17, 2026, 12:58 PM UTC

    We are continuing to work on a fix for this issue. Customers may still experience login failures with unified identity in this realm while we validate recovery. We will provide another update as soon as more information is available.

  5. identified Apr 17, 2026, 01:17 PM UTC

    We are still continuing to work on a fix for this issue. Customers may still experience login failures with unified identity in this realm while we validate recovery. We will provide another update as soon as more information is available.

  6. monitoring Apr 17, 2026, 01:38 PM UTC

    The mitigation has been completed and unified identity login access has been restored in this realm. We are no longer seeing the login failures. We will continue to monitor to ensure stability.

  7. resolved Apr 17, 2026, 05:46 PM UTC

    This incident has been resolved.