Splunk Observability Cloud JP0 incident

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

Critical Resolved View vendor source →

Splunk Observability Cloud JP0 experienced a critical incident on April 17, 2026 affecting SSO OIDC Endpoint, lasting 1h 45m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2026, 11:51 AM UTC
Resolved
Apr 17, 2026, 01:37 PM UTC
Duration
1h 45m
Detected by Pingoru
Apr 17, 2026, 11:51 AM UTC

Affected components

SSO OIDC Endpoint

Update timeline

  1. investigating Apr 17, 2026, 11:50 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, 11:51 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.

  3. investigating Apr 17, 2026, 12:19 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.

  4. identified Apr 17, 2026, 12:30 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.

  5. 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.

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

    A fix is being rolled out for the unified identity login issue in this realm. You may still see some intermittent login failures while the update propagates across all services. We are monitoring recovery and will share another update once validation is complete.

  7. monitoring Apr 17, 2026, 01:28 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.

  8. monitoring Apr 17, 2026, 01:28 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.

  9. resolved Apr 17, 2026, 01:37 PM UTC

    This incident has been resolved.