SignalFx US0 incident
Customers are not able login using Splunk Cloud (SCS) unified identify login page
SignalFx US0 experienced a minor incident on April 17, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- monitoring Apr 17, 2026, 05:46 PM UTC
Apr 17, 10:46 PDT Resolved - This incident has been resolved. Apr 17, 06:38 PDT Monitoring - 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. Apr 17, 06:17 PDT Update - 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. Apr 17, 05:58 PDT Update - 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. Apr 17, 05:31 PDT Identified - 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. Apr 17, 05:18 PDT Update - 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. Apr 17, 01:30 PDT Investigating - 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.