Is Splunk Observability Cloud JP0 down?
Last checked 8m agoNo incidents right now.
Splunk Observability Cloud JP0 is operational right now. Last checked 8m ago; the most recent incident resolved 22d ago.
Real-time Splunk Observability Cloud JP0 status, recent outages, and incident history — pulled directly from Splunk Observability Cloud JP0's official status page at https://status.jp0.signalfx.com every 5 minutes. Pingoru tracks 54 Splunk Observability Cloud JP0 services and has captured 5 incidents in the last 90 days (99.94% uptime). Get email, Slack, Discord, or webhook alerts the moment Splunk Observability Cloud JP0 reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · Jul 08, 2026, 10:49 AM UTC
Between 1a PDT and 2:50a PDT, any GCP integration that had the "Sync all (dynamically) listed projects" setting enabled had some of the Cloud Monitoring data from GCP dropped. This issue has been resolved. Customers may see gaps in charts and detectors that use affected GCP Cloud Monitoring metrics. AWS CloudWatch and Azure Monitor metrics are not impacted.
Latest: Between 1a PDT and 2:50a PDT, any GCP integration that had the "Sync all (dynamically) listed projects" setting enabled had some of the Cloud Monitoring data from GCP dropped. This…
-
- Splunk APM Tag Spotlight
Timeline · 1 update
- resolved · Jul 01, 2026, 03:06 PM UTC
We have confirmed that the issue affecting Tag Spotlight has been resolved. Customers may have experienced limited functionality within Tag Spotlight beginning at approximately 4:30 PM PT on June 30. Full functionality was restored at 7:20 AM PT on July 1.
Latest: We have confirmed that the issue affecting Tag Spotlight has been resolved. Customers may have experienced limited functionality within Tag Spotlight beginning at approximately 4:3…
-
-
Timeline · 1 update
- resolved · Jun 26, 2026, 07:33 AM UTC
Due to a regression in a recent release, users navigating from Logs Related Content on the APM TraceView page to Log Observer were redirected back to APM TraceView instead. This impacted the Logs Correlation experience for customers across all realms, except US3 and Gov. The change has been reverted to restore the expected navigation experience. Product availability for APM and Log Observer was not impacted; the issue was limited to the Logs Correlation workflow from TraceView. Incident Start Time: 05:09 PDT, June 25, 2026 Incident End Time: 22:15 PDT, June 25, 2026
Latest: Due to a regression in a recent release, users navigating from Logs Related Content on the APM TraceView page to Log Observer were redirected back to APM TraceView instead. This im…
-
- Splunk Synthetics Monitoring Results processing
Timeline · 5 updates
- investigating · Jun 02, 2026, 09:45 AM UTC
We are investigating delays in processing Splunk Observability Synthetic Monitoring test results. Tests are still running, but metrics may be delayed until the issue is resolved.
- investigating · Jun 02, 2026, 10:45 AM UTC
We are continuing the investigation on the delays in processing Splunk Observability Synthetic Monitoring test results. Tests are still running, but metrics could be delayed until the issue is resolved. Splunk teams are engaged and investigating.
- investigating · Jun 02, 2026, 11:45 AM UTC
We are continuing the investigation on the delays in processing Splunk Observability Synthetic Monitoring test results. Tests are still running, but metrics could be delayed until the issue is resolved. Splunk teams are investigating and troubleshooting.
- investigating · Jun 02, 2026, 12:57 PM UTC
We are investigating delays in processing Splunk Observability Synthetic Monitoring test results for a small subset of customers. Tests are still running, but metrics may be delayed until the issue is resolved.
- resolved · Jun 02, 2026, 04:44 PM UTC
We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank you for your patience. Time range of impact: June 1 17:30 UTC - June 2 14:30 UTC
Latest: We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank yo…
-
- Started Jul 08, 2026, 10:49 AM UTC · Resolved Jul 08, 2026, 05:00 AM UTC · —
- Started Jul 01, 2026, 03:06 PM UTC · Resolved Jul 01, 2026, 03:06 PM UTC · —
- Started Jun 26, 2026, 07:33 AM UTC · Resolved Jun 25, 2026, 12:00 PM UTC · —
- Started Jun 02, 2026, 09:45 AM UTC · Resolved Jun 02, 2026, 04:44 PM UTC · 6h 58m