Splunk Observability Cloud JP0 Outage History

Splunk Observability Cloud JP0 degraded View live status →

There were 6 Splunk Observability Cloud JP0 outages since February 17, 2026 totaling 855h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.jp0.signalfx.com

Critical April 25, 2026

RUM MMS Data Drop — Missing Chart & Dashboard Data

Detected by Pingoru
Apr 25, 2026, 03:36 PM UTC
Resolved
Apr 26, 2026, 12:53 AM UTC
Duration
9h 16m
Affected: Splunk RUM Monitoring MetricSets
Timeline · 6 updates
  1. investigating Apr 25, 2026, 03:36 PM UTC

    We are investigating an issue affecting Real User Monitoring (RUM) metrics across all realms. Customers may experience custom metric MTS quota limits being exceeded, resulting in metric data being dropped. RUM metric dimensions that were previously available may be missing.

  2. identified Apr 25, 2026, 05:05 PM UTC

    The issue affecting Real User Monitoring (RUM) metrics has been identified. The fix is currently being implemented. We are actively working to restore full service and will provide further updates as progress continues.

  3. identified Apr 25, 2026, 06:35 PM UTC

    We are continuing to work on the fix. We expect to have further updates within the next hour. We appreciate your patience as we work diligently to resolve this issue and restore full service.

  4. identified Apr 25, 2026, 10:24 PM UTC

    We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We are thoroughly validating the mitigation to ensure it resolves the issue effectively and maintains system stability. We appreciate your ongoing patience and will provide further updates as testing progresses.

  5. identified Apr 25, 2026, 11:46 PM UTC

    We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We will share an update once we have further information.

  6. resolved Apr 26, 2026, 12:53 AM UTC

    The outage impacting RUM MMS Data Drop has been resolved after internal engineering teams deployed a fix. All systems are operational and stable. Thank you for your patience and understanding.

Read the full incident report →

Critical April 17, 2026

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

Detected by Pingoru
Apr 17, 2026, 11:51 AM UTC
Resolved
Apr 17, 2026, 01:37 PM UTC
Duration
1h 45m
Affected: SSO OIDC Endpoint
Timeline · 9 updates
  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.

Read the full incident report →

Critical April 5, 2026

Splunk Cloud Unified Identity Unavailable

Detected by Pingoru
Apr 05, 2026, 06:29 PM UTC
Resolved
Apr 05, 2026, 07:47 PM UTC
Duration
1h 17m
Affected: Splunk Log Observer Interface
Timeline · 7 updates
  1. investigating Apr 05, 2026, 06:29 PM UTC

    We are investigating a major outage of Splunk cloud involving logging in via Unified Identity. Ingest is not impacted at this time. We will provide an update as soon as possible. Splunk Log Observer may not be available for unified identity customers.

  2. investigating Apr 05, 2026, 06:45 PM UTC

    Our team is currently working to resolve an issue impacting Unified Identity services.

  3. investigating Apr 05, 2026, 07:01 PM UTC

    Investigation into the root cause of the Unified Identity issue is ongoing.

  4. identified Apr 05, 2026, 07:15 PM UTC

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

  5. identified Apr 05, 2026, 07:32 PM UTC

    Teams continue working to implement the fix for this issue.

  6. monitoring Apr 05, 2026, 07:39 PM UTC

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

  7. resolved Apr 05, 2026, 07:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 23, 2026

Synthetics tests running from Bahrain may not run on schedule

Detected by Pingoru
Mar 23, 2026, 11:33 PM UTC
Resolved
Apr 25, 2026, 02:53 AM UTC
Duration
32d 3h
Affected: Splunk Synthetics Monitoring Runners
Timeline · 4 updates
  1. identified Mar 23, 2026, 11:33 PM UTC

    The issue has been identified and is due to a Cloud Provider outage in the Bahrain region.

  2. identified Mar 24, 2026, 12:54 AM UTC

    The issue has been identified as an outage affecting the Bahrain region due to a Cloud Provider outage. We recommend that users temporarily run their Synthetic Monitoring tests from an alternative location while this issue is being resolved by the Cloud Provider.

  3. identified Mar 24, 2026, 06:18 PM UTC

    The issue has been identified as a regional cloud provider outage that is impacting our ability to maintain Synthetics testing in specific areas. Due to the uncertainty regarding the resolution timeline for this issue, we have made the decision to temporarily remove the following locations from our Synthetics testing network: Bahrain Muscat UAE We recommend reviewing your current test configurations and selecting alternative testing locations if necessary to ensure continued coverage. Our engineering team is monitoring the situation closely. We will provide further updates as more information becomes available from the cloud provider. We apologize for any inconvenience this may cause and appreciate your patience as we work to maintain the reliability of our services.

  4. resolved Apr 25, 2026, 02:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Potential Cloud Integration Issues In UAE Region

Detected by Pingoru
Mar 02, 2026, 08:16 PM UTC
Resolved
Mar 05, 2026, 07:22 PM UTC
Duration
2d 23h
Timeline · 3 updates
  1. monitoring Mar 02, 2026, 08:16 PM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  2. monitoring Mar 03, 2026, 05:12 PM UTC

    Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

  3. resolved Mar 05, 2026, 07:22 PM UTC

    Monitoring over the past several days has not identified any impact to Splunk Observability Cloud services related to the previously reported cloud service provider disruption in the Middle East. Splunk Observability Cloud services continue to operate normally. We will continue to monitor the situation and will notify customers if conditions change.

Read the full incident report →

Major February 17, 2026

Data Management Page is not loading

Detected by Pingoru
Feb 17, 2026, 06:24 PM UTC
Resolved
Feb 17, 2026, 07:23 PM UTC
Duration
59m
Affected: Splunk Observability Cloud Web Interface
Timeline · 4 updates
  1. investigating Feb 17, 2026, 06:24 PM UTC

    Customers may be experiencing errors while loading Data Management Page.

  2. identified Feb 17, 2026, 06:49 PM UTC

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

  3. monitoring Feb 17, 2026, 07:14 PM UTC

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

  4. resolved Feb 17, 2026, 07:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Splunk Observability Cloud JP0 downtime and outages?

Pingoru polls Splunk Observability Cloud JP0's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Splunk Observability Cloud JP0 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Splunk Observability Cloud JP0 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Splunk Observability Cloud JP0 for free

5 free monitors · No credit card required