Splunk Observability Cloud US1 Realm
All Systems Operational
Splunk Observability Cloud Web Interface Operational
90 days ago
99.81 % uptime
Today
Datapoint Ingest Operational
90 days ago
99.99 % uptime
Today
Splunk Observability Cloud API Operational
90 days ago
99.91 % uptime
Today
Alerting Operational
90 days ago
99.99 % uptime
Today
Splunk APM Operational
90 days ago
99.99 % uptime
Today
Splunk APM Ingest ? Operational
90 days ago
100.0 % uptime
Today
Splunk APM Interface ? Operational
90 days ago
99.98 % uptime
Today
Splunk APM Monitoring MetricSets ? Operational
90 days ago
99.98 % uptime
Today
Splunk APM Troubleshooting MetricSets ? Operational
90 days ago
100.0 % uptime
Today
Splunk APM Trace Data ? Operational
90 days ago
100.0 % uptime
Today
Splunk APM Tag Spotlight ? Operational
90 days ago
100.0 % uptime
Today
Splunk APM Business Workflows ? Operational
90 days ago
100.0 % uptime
Today
Splunk APM API ? Operational
90 days ago
100.0 % uptime
Today
Splunk RUM Operational
90 days ago
99.99 % uptime
Today
Splunk RUM Ingest ? Operational
90 days ago
100.0 % uptime
Today
Splunk RUM Interface ? Operational
90 days ago
99.99 % uptime
Today
Splunk RUM Metrics Operational
90 days ago
100.0 % uptime
Today
Splunk RUM API Operational
90 days ago
100.0 % uptime
Today
Splunk Observability Cloud µAPM PG Operational
90 days ago
100.0 % uptime
Today
µAPM PG Interface ? Operational
90 days ago
100.0 % uptime
Today
µAPM PG Ingest ? Operational
90 days ago
100.0 % uptime
Today
µAPM PG API ? Operational
90 days ago
100.0 % uptime
Today
3rd Party Services Operational
AWS ec2-us-west-2 Operational
AWS elb-us-west-2 Operational
AWS s3-us-west-2 Operational
PagerDuty Notification Delivery Operational
PagerDuty Events API Operational
Slack Notifications Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
We are always looking for ways to improve our security and that of our customers. As such, on August 31, 2021, Splunk Observability Cloud is disabling support for outbound connections using HTTP and ones that use deprecated versions of HTTPS TLS which include SSL (1.0, 2.0, and 3.0) and TLS 1.0 and 1.1. This change affects the Splunk Observability Cloud integrations and notifications, webhooks, email (SMTP) servers, and SSO/SAML connections.

This change affects all Splunk Observability products including:
- Splunk Infrastructure Monitoring (IM)
- Splunk Application Performance Monitoring (APM)
- Splunk Real User Monitoring (RUM)
- Splunk Log Observer

Customers that have configured HTTPS for these connections and are using TLS 1.2+ are not affected. After August 31, 2021, connections that are using HTTP or HTTPS with earlier than TLS 1.2 will stop functioning.

If you believe you are affected by this change, please ensure your systems and configuration are updated before this change occurs. If you have any questions please feel free to contact your Splunk representative, open a support case using the in-app support portal, or send an email to observability-support@splunk.com.
Posted on Jul 29, 12:21 PDT
End-to-End Processing Time (Average) ?
Fetching
Splunk APM Interface Response Time (Average) ?
Fetching
API Health Check Response Time (Average) ?
Fetching
Past Incidents
Jul 30, 2021

No incidents reported today.

Jul 29, 2021

No incidents reported.

Jul 28, 2021
Resolved - This incident has been resolved.
Jul 28, 21:37 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 28, 21:17 PDT
Update - We are continuing to work on a fix for this issue.
Jul 28, 21:08 PDT
Identified - We have identified the root cause of this issue and have deployed the fix and are recovering.
Jul 28, 19:06 PDT
Investigating - A degradation in the performance of the Splunk RUM trace data ingestion pipeline is causing the processing and storage of traces to be delayed by more than five minutes. No data is being lost at this time, but the most recent data may not be available.
Jul 28, 19:05 PDT
Jul 27, 2021

No incidents reported.

Jul 26, 2021

No incidents reported.

Jul 25, 2021

No incidents reported.

Jul 24, 2021

No incidents reported.

Jul 23, 2021

No incidents reported.

Jul 22, 2021

No incidents reported.

Jul 21, 2021
Resolved - This incident has been resolved.
Jul 21, 16:01 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 21, 15:46 PDT
Update - We have checked in a fix and expect the delay to be resolved in the next 40 minutes. This is only impacting a small portion of the traffic (roughly 1%).
Jul 21, 14:56 PDT
Identified - The issue has been identified and a fix is being implemented.
Jul 21, 14:36 PDT
Investigating - 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.
Jul 21, 14:29 PDT
Jul 20, 2021

No incidents reported.

Jul 19, 2021

No incidents reported.

Jul 18, 2021

No incidents reported.

Jul 17, 2021

No incidents reported.

Jul 16, 2021
Resolved - This incident has been resolved. About 2% of datapoints received were dropped during the incident, between 10:48am and 11:00am US/Pacific.
Jul 16, 11:43 PDT
Monitoring - The system has recovered and we are continuing to monitor its performance.
Jul 16, 11:11 PDT
Investigating - Datapoint ingest is affected and we are dropping datapoints. We are investigating and will provide an update every 15 mins.
Jul 16, 11:02 PDT
Resolved - This incident has been resolved.
Jul 16, 03:27 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 16, 03:11 PDT
Identified - We have identified a degradation in our REST API that can cause some customers to experience failures when attempting to edit charts or detectors. Our team is working on resolving the issue.
Jul 16, 01:59 PDT