Splunk Observability Cloud JP0 Outage History

Splunk Observability Cloud JP0 is up right now

Pingoru has recorded 51 incidents for Splunk Observability Cloud JP0: 17 in the last 12 months and 3 in the last 90 days.

Source: status.jp0.signalfx.com

51incidents recorded
17last 12 months
3last 90 days
2 daystypical duration
Incidents per month
024AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Splunk Observability Cloud JP0 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20264157 of 720 (22%)
May 202600 of 744 (0%)
June 2026224 of 720 (3%)
July 202620 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202627 of 574 (1%)

Incidents, newest first

Minor April 15, 2025 Splunk APM Troubleshooting MetricSets Delayed 1h 39m Splunk APM Troubleshooting MetricSets, Splunk APM Trace Data, Splunk APM Tag Spotlight, Splunk APM Business Workflows

Started Apr 15, 2025, 07:45 AM UTC· resolved Apr 15, 2025, 09:25 AM UTC

  1. investigating Apr 15, 2025, 09:25 AM UTC

    A degradation in the performance of the Splunk APM trace processing pipeline is causing Troubleshooting MetricSets to be delayed by more than five minutes. As a result, the APM Troubleshooting experience, service maps and Tag Spotlight do not have access to the most recent data. The processing of metrics for Business Workflows, which also depends on this pipeline, are equally delayed. Trace data ingest is not impacted at this time; service-level and endpoint-level Monitoring MetricSets and the detectors built from them are also not impacted.

  2. identified Apr 15, 2025, 09:27 AM UTC

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

  3. resolved Apr 15, 2025, 09:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2025 Unable to fetch Splunk RUM sessions 2h 59m Splunk RUM API

Started Apr 15, 2025, 01:15 AM UTC· resolved Apr 15, 2025, 04:15 AM UTC

  1. investigating Apr 15, 2025, 05:06 AM UTC

    We are currently investigating this issue.

  2. identified Apr 15, 2025, 05:07 AM UTC

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

  3. resolved Apr 15, 2025, 05:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 14, 2025 Splunk Synthetics runners are unavailable in the Stockholm region 4h 2m Splunk Synthetics Monitoring Runners

Started Feb 14, 2025, 12:20 AM UTC· resolved Feb 14, 2025, 04:22 AM UTC

  1. identified Feb 14, 2025, 12:20 AM UTC

    Splunk Synthetics runners are unavailable in the Stockholm region due to an AWS EC2 instance outage in the eu-north-1 region.

  2. monitoring Feb 14, 2025, 12:45 AM UTC

    We are seeing signs of recovery and are continuing to monitor.

  3. monitoring Feb 14, 2025, 02:30 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 14, 2025, 04:22 AM UTC

    This incident has been resolved.

Read the full incident report →