IsDown continuously monitor the official Splunk Observability Cloud US2 status page for ongoing outages. Check the stats for the latest 30 days and a list of the last Splunk Observability Cloud US2 outages.
Number of Outages
1
Average Downtime
0 mins
Total Downtime
0 mins
Since last incident
23 days
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Splunk Observability Cloud US2, and never miss an outage again.
Minor · started 23 days ago
A recent code push resulted in some sf.org metrics reporting incorrectly that data was being dropped. No data drops actually occurred. The code change has been rolled back and the metrics are now being correctly reported. This issue started around 8:10 AM PT and was resolved by 10:15 AM PT. Again, no production outage actually happened only sf.org metrics are reporting incorrect information. We apologize for this inconvenience. Impacted metrics: - sf.org.numDatapointsDroppedBatchSizeByToken - sf.org.numDatapointsDroppedBatchSize
Minor · started about 2 months ago
Data management for integrations list affected
Minor · started 2 months ago
We are investigating some issues with usage and throttling metrics generated for Splunk APM that might lead to inconsistencies in any charts that use them. Trace data is not impacted and continues to be processed as expected.
Major · started 3 months ago
A degradation in the performance of the Splunk APM data ingestion pipeline is causing the processing and storage of raw trace data to be delayed by more than five minutes. No data is being lost at this time and MetricSets are not impacted but the most recent data may not be available in trace search results.
Major · started 3 months ago
We are investigating a major outage of the Splunk Observability Cloud web application. Data ingest is not impacted at this time. We will provide an update as soon as possible.
Major · started 3 months ago
Datapoint ingest is affected and we are dropping datapoints. We are investigating and will provide an update every 15 mins.
Minor · started 4 months ago
Splunk RUM ingestion was affected from 6:04 AM until 6:23 AM PT resulting in dropped spans. All other ingestion endpoints including datapoints and APM spans were not impacted. The incident is now resolved.
Minor · started 4 months ago
A degradation in the performance of the Splunk RUM trace processing pipeline caused Troubleshooting MetricSets to be delayed from 10:15 AM until 10:45 AM PT. As a result, the RUM Troubleshooting experience did not have access to the most recent data at that time.
Get notified only when an outage impacts a certain component.
The data and notifications you need, in the tools you already use.
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Splunk Observability Cloud US2, and never miss an outage again.
Try it out! How much time you'll save your team, by having the outages information close to them?