Is Splunk Observability Cloud JP0 down?

Last checked 4m ago
Current status
Splunk Observability Cloud JP0 has degraded performance

Affected component: Splunk Synthetics Monitoring Runners

Get alerts when Splunk Observability Cloud JP0 breaks →

Free · no credit card

Official status page: https://status.jp0.signalfx.com · Polled every 5 minutes · 54 components tracked

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 7 incidents in the last 90 days (99.70% 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.

Users who monitor Splunk Observability Cloud JP0 also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Splunk Observability Cloud JP0 uptime 99.70% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. RUM MMS Data Drop — Missing Chart & Dashboard Data
    Resolved 9h 16m
    Started Apr 25, 2026, 03:36 PM UTC · Resolved Apr 26, 2026, 12:53 AM UTC
    Splunk RUM Monitoring MetricSets
    6 updates · show timeline
    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    • 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.

    Latest: 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 un…

  2. RUM MMS Data Drop — Missing Chart & Dashboard Data
    Resolved 2h 10m
    Started Apr 25, 2026, 01:01 AM UTC · Resolved Apr 25, 2026, 03:11 AM UTC
    Splunk RUM Monitoring MetricSets
    6 updates · show timeline
    • investigating · Apr 25, 2026, 01:01 AM UTC

      We are currently investigating an issue where RUM (Real User Monitoring) MMS data is being dropped, which may result in missing or incomplete data in charts and dashboards related to real user monitoring. We are actively investigating and will provide updates as the situation develops.

    • identified · Apr 25, 2026, 01:21 AM UTC

      We have identified the cause of the issue resulting in missing or incomplete data in Real User Monitoring charts and dashboards. We are implementing a fix and will provide an update within 15 minutes.

    • identified · Apr 25, 2026, 02:01 AM UTC

      A solution to address the issue causing missing or incomplete data in Real User Monitoring (RUM) charts and dashboards is currently being implemented. Our teams are actively working on deploying the fix and will continue to provide updates as progress is made

    • identified · Apr 25, 2026, 02:32 AM UTC

      We have identified an issue causing missing or incomplete data in Real User Monitoring (RUM) custom charts and dashboards across multiple realms. A fix is currently being rolled out and validated

    • monitoring · Apr 25, 2026, 02:54 AM UTC

      A fix for the issue affecting Real User Monitoring (RUM) charts and dashboards has been deployed and is being actively monitored across all realms; customers may now see data restored in charts and dashboards

    • resolved · Apr 25, 2026, 03:11 AM UTC

      The issue affecting Real User Monitoring (RUM) custom charts and dashboards across multiple realms has been resolved. The fix has been deployed, and data is now flowing normally.

    Latest: The issue affecting Real User Monitoring (RUM) custom charts and dashboards across multiple realms has been resolved. The fix has been deployed, and data is now flowing normally.

  3. Synthetics tests running from Bahrain may not run on schedule
    Resolved 32d 3h
    Started Mar 23, 2026, 11:33 PM UTC · Resolved Apr 25, 2026, 02:53 AM UTC
    Splunk Synthetics Monitoring Runners
    4 updates · show timeline
    • 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.

    • 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.

    • 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.

    • resolved · Apr 25, 2026, 02:53 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Splunk Observability Cloud JP0 outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 5 incidents
  • RUM MMS Data Drop — Missing Chart & Dashboard Data Resolved
    Started Apr 25, 2026, 03:36 PM UTC · Resolved Apr 26, 2026, 12:53 AM UTC · 9h 16m
  • RUM MMS Data Drop — Missing Chart & Dashboard Data Resolved
    Started Apr 25, 2026, 01:01 AM UTC · Resolved Apr 25, 2026, 03:11 AM UTC · 2h 10m
  • Customers are not able login using Splunk Cloud (SCS) unified identify login page Resolved
    Started Apr 17, 2026, 11:51 AM UTC · Resolved Apr 17, 2026, 01:37 PM UTC · 1h 45m
  • Splunk Cloud Unified Identity Unavailable Resolved
    Started Apr 05, 2026, 06:29 PM UTC · Resolved Apr 05, 2026, 07:47 PM UTC · 1h 17m
  • Synthetics tests running from Bahrain may not run on schedule Resolved
    Started Mar 23, 2026, 11:33 PM UTC · Resolved Apr 25, 2026, 02:53 AM UTC · 32d 3h

See Splunk Observability Cloud JP0 in your Pingoru dashboard

Monitor Splunk Observability Cloud JP0 alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Splunk Observability Cloud JP0 to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Splunk Observability Cloud JP0 incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Splunk Observability Cloud JP0 or see every provider at once.

Maintenance calendar

Scheduled Splunk Observability Cloud JP0 maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Splunk Observability Cloud JP0 status change, one inbox

Pingoru watches Splunk Observability Cloud JP0's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Splunk Observability Cloud JP0 reports on 54 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Splunk Observability Cloud JP0 alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Splunk Observability Cloud JP0 maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Splunk Observability Cloud JP0 services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Splunk Observability Cloud JP0 from the same account, with per-user notification preferences for any monitor.

Get notified on Splunk Observability Cloud JP0 status changes

Pingoru watches Splunk Observability Cloud JP0's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Splunk Observability Cloud JP0 free

Monitor Splunk Observability Cloud JP0 along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Splunk Observability Cloud JP0 and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Splunk Observability Cloud JP0 uptime & incident history

See 90 days of Splunk Observability Cloud JP0 uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Splunk Observability Cloud JP0 uptime history

Frequently asked questions

What is Splunk Observability Cloud JP0's uptime?
Over the last 90 days, Splunk Observability Cloud JP0 reported 99.70% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.jp0.signalfx.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Splunk Observability Cloud JP0's uptime history rolling forward in real time.
Has Splunk Observability Cloud JP0 had outages in 2026?
Yes — Splunk Observability Cloud JP0 has had 7 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Splunk Observability Cloud JP0 outage?
The most recent Splunk Observability Cloud JP0 incident was "RUM MMS Data Drop — Missing Chart & Dashboard Data", which started on April 25, 2026 and was resolved on April 26, 2026. Pingoru captured this directly from https://status.jp0.signalfx.com. See the full incident card above for affected components and the update timeline.
How often does Splunk Observability Cloud JP0 have outages?
Based on the last 90 days, Splunk Observability Cloud JP0 averages 2.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Splunk Observability Cloud JP0's status page?
Splunk Observability Cloud JP0's official status page is https://status.jp0.signalfx.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Splunk Observability Cloud JP0 down right now?
Splunk Observability Cloud JP0 has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Splunk Observability Cloud JP0 reports a change. Current status is based on 54 tracked services.
How does Pingoru know if Splunk Observability Cloud JP0 is down?
We read https://status.jp0.signalfx.com directly, using Splunk Observability Cloud JP0's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Splunk Observability Cloud JP0 has an outage?
Create a free Pingoru account and add Splunk Observability Cloud JP0 as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Splunk Observability Cloud JP0's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Splunk Observability Cloud JP0 incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Splunk Observability Cloud JP0 issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Splunk Observability Cloud JP0 status?
We use Splunk Observability Cloud JP0's own status page at https://status.jp0.signalfx.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Degraded" mean?
Splunk Observability Cloud JP0 is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch Splunk Observability Cloud JP0's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Splunk Observability Cloud JP0 free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →