Splunk OnCall incident

Splunk On-Call is experiencing disruptions for Single Sign On (SSO) functionality

Major Resolved View vendor source →

Splunk OnCall experienced a major incident on October 26, 2024 affecting Single Sign On, lasting 1h 18m. The incident has been resolved; the full update timeline is below.

Started
Oct 26, 2024, 09:45 AM UTC
Resolved
Oct 26, 2024, 11:03 AM UTC
Duration
1h 18m
Detected by Pingoru
Oct 26, 2024, 09:45 AM UTC

Affected components

Single Sign On

Update timeline

  1. investigating Oct 26, 2024, 09:45 AM UTC

    Please bear with us while we investigate this issue—impacted components Single Sign On (SSO) Updates to follow. We apologize for this inconvenience. Please reach out to On-Call Support with any questions. https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/

  2. identified Oct 26, 2024, 10:23 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 26, 2024, 10:52 AM UTC

    A fix has been implemented and we are monitoring the solution. SSO is back to an operational state.

  4. resolved Oct 26, 2024, 11:03 AM UTC

    This incident has been resolved. Single Sign On (SSO) is fully operational. We apologize for this inconvenience. If you continue to experience issues with your SSO connections, please reach out to On-Call Support as soon as possible! https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/