SignalFx US0 incident

Splunk Observability Cloud Web Interface Unavailable

Major Resolved View vendor source →

SignalFx US0 experienced a major incident on August 29, 2025 affecting Splunk Observability Cloud Web Interface and Splunk Observability Cloud API, lasting 5h 39m. The incident has been resolved; the full update timeline is below.

Started
Aug 29, 2025, 05:18 PM UTC
Resolved
Aug 29, 2025, 10:57 PM UTC
Duration
5h 39m
Detected by Pingoru
Aug 29, 2025, 05:18 PM UTC

Affected components

Splunk Observability Cloud Web InterfaceSplunk Observability Cloud API

Update timeline

  1. investigating Aug 29, 2025, 05:18 PM UTC

    Customers may be experiencing delays in some charts and detectors. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

  2. investigating Aug 29, 2025, 05:30 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 29, 2025, 05:31 PM UTC

    Charts for all customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

  4. investigating Aug 29, 2025, 05:45 PM UTC

    Charts for all customers may not be loading. API may be inaccessible. Datapoint ingest is not affected. We are continuing to investigate and will provide an update shortly.

  5. monitoring Aug 29, 2025, 06:14 PM UTC

    The system is recovering. Customers may still be experiencing delays or inaccessibility in API access, charts and detectors. Datapoint ingest is not affected.

  6. monitoring Aug 29, 2025, 07:08 PM UTC

    We are continuing to monitor for any further issues.

  7. identified Aug 29, 2025, 07:09 PM UTC

    We are continuing to work on addressing this issue.

  8. identified Aug 29, 2025, 08:06 PM UTC

    We are continuing to work on addressing this issue. At this time, users should see early signs of recovery in being able to access the Splunk Observability Cloud UI and API. Charts and Detectors relying on recent data are delayed at this time as the backlog catches up.

  9. identified Aug 29, 2025, 08:31 PM UTC

    We are continuing to work on a fix for this issue.

  10. monitoring Aug 29, 2025, 08:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  11. monitoring Aug 29, 2025, 09:46 PM UTC

    All systems are now operating as expected, and we are continuing to monitor for any further issues.

  12. resolved Aug 29, 2025, 10:57 PM UTC

    This incident has been resolved.