- Detected by Pingoru
- Oct 15, 2026, 06:55 PM UTC
- Resolved
- Oct 15, 2026, 09:20 PM UTC
- Duration
- 2h 24m
Affected: Splunk Observability Cloud Web Interface
Timeline · 4 updates
-
investigating Oct 15, 2026, 06:55 PM UTC
We are investigating a degradation of the Splunk Observability Cloud web application for some customers. Data ingest is not impacted at this time. We will provide an update as soon as possible.
-
investigating Oct 15, 2026, 08:00 PM UTC
Our engineering teams are actively troubleshooting the identified performance problems in the Splunk Observability Web UI, we will share a new update as soon as possible.
-
monitoring Oct 15, 2026, 08:33 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 15, 2026, 09:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 12, 2026, 07:48 PM UTC
- Resolved
- Oct 12, 2026, 09:42 PM UTC
- Duration
- 1h 53m
Affected: Splunk APM Trace Data
Timeline · 3 updates
-
identified Oct 12, 2026, 07:48 PM UTC
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.
-
monitoring Oct 12, 2026, 09:00 PM UTC
We are monitoring recovery.
-
resolved Oct 12, 2026, 09:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2026, 08:39 PM UTC
- Resolved
- Oct 07, 2026, 09:20 PM UTC
- Duration
- 41m
Affected: Splunk Observability Cloud Web Interface
Timeline · 3 updates
-
investigating Oct 07, 2026, 08:39 PM UTC
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.
-
identified Oct 07, 2026, 09:12 PM UTC
The issue has been identified and a remediation is in progress.
-
resolved Oct 07, 2026, 09:20 PM UTC
Steps to remediation have recovered login access.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2026, 08:18 PM UTC
- Resolved
- Oct 07, 2026, 09:23 PM UTC
- Duration
- 1h 4m
Affected: Splunk Observability Cloud Web InterfaceAlerting
Timeline · 4 updates
-
investigating Oct 07, 2026, 08:18 PM UTC
Customers may be experiencing delays in seeing newly created dimension, updated dimension, and alerts. Team is currently investigating the issue.
-
identified Oct 07, 2026, 08:25 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Oct 07, 2026, 09:12 PM UTC
The issue has been identified and a remediation is in progress.
-
resolved Oct 07, 2026, 09:23 PM UTC
W have verified that the fix has recovered service.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2026, 06:46 PM UTC
- Resolved
- Oct 07, 2026, 09:35 PM UTC
- Duration
- 2h 49m
Affected: MCP
Timeline · 7 updates
-
investigating Oct 07, 2026, 06:46 PM UTC
We're experiencing connectivity issues with the Splunk Observability MCP server, which may affect the availability of some tools. We're actively investigating the issue
-
investigating Oct 07, 2026, 07:16 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available.
-
investigating Oct 07, 2026, 07:59 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
-
investigating Oct 07, 2026, 08:36 PM UTC
Our engineering teams continue troubleshooting connectivity issues with the Splunk Observability MCP server. We will share additional information as it becomes available
-
monitoring Oct 07, 2026, 09:12 PM UTC
Engineering teams have deployed a fix and service recovery is progressing. We will continue monitoring and share an update by 22:00 UTC.
-
monitoring Oct 07, 2026, 09:13 PM UTC
We are continuing to monitor for any further issues.
-
resolved Oct 07, 2026, 09:35 PM UTC
Service recovery fully confirmed, we are now considering this resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 03, 2026, 02:20 AM UTC
- Resolved
- Oct 03, 2026, 03:12 AM UTC
- Duration
- 51m
Affected: Splunk Synthetics Monitoring Results processing
Timeline · 4 updates
-
investigating Oct 03, 2026, 02:55 AM UTC
We are investigating delays in processing Splunk Observability Synthetic Monitoring test results. Synthetic Monitoring tests are operational but metrics may be missing until the issue is resolved.
-
identified Oct 03, 2026, 03:03 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 03, 2026, 03:12 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 03, 2026, 03:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 12:34 PM UTC
- Resolved
- Sep 25, 2026, 03:07 PM UTC
- Duration
- 2h 32m
Affected: Splunk APM Interface
Timeline · 4 updates
-
investigating Sep 25, 2026, 12:34 PM UTC
We are currently investigating this issue.
-
identified Sep 25, 2026, 01:00 PM UTC
The issue has been identified and a fix is being implemented.
-
identified Sep 25, 2026, 02:02 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Sep 25, 2026, 03:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2026, 03:00 PM UTC
- Resolved
- Sep 18, 2026, 03:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 18, 2026, 03:07 PM UTC
We are seeing login failures due to certificate issues. It has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 12, 2026, 03:16 AM UTC
- Resolved
- Sep 12, 2026, 03:30 AM UTC
- Duration
- 14m
Affected: Datapoint Ingest
Timeline · 2 updates
-
investigating Sep 12, 2026, 03:16 AM UTC
Datapoint ingest is affected and we are dropping datapoints for new time-series. We are investigating and will provide an update every 15 mins.
-
resolved Sep 12, 2026, 03:30 AM UTC
Between 7:37 PM and 8:17 PM PST, a small number of data points for new time series were not accepted. As a result, new time series may have experienced a delay of approximately 20–25 minutes before becoming available in charting and detectors. APM and RUM ingestion were not impacted.
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 11:09 PM UTC
- Resolved
- Aug 25, 2026, 12:20 AM UTC
- Duration
- 1h 11m
Affected: Alerting
Timeline · 3 updates
-
investigating Aug 24, 2026, 11:09 PM UTC
From 3:08PM PDT, customers may experience delays in seeing newly created MetricTimeSeries. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
-
investigating Aug 25, 2026, 12:20 AM UTC
We've identified that this incident was a false alarm due to rate limiting applied to a single tenant. We have reached out to the affected tenant. All other customers within US0 are not and have not been impacted by this incident.
-
resolved Aug 25, 2026, 12:20 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 03:46 AM UTC
- Resolved
- Jul 31, 2026, 04:32 AM UTC
- Duration
- 46m
Affected: Splunk APM InterfaceSplunk APM Monitoring MetricSets
Timeline · 4 updates
-
investigating Jul 31, 2026, 03:46 AM UTC
A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be dropped. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.
-
identified Jul 31, 2026, 04:07 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 31, 2026, 04:08 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 31, 2026, 04:32 AM UTC
The issue has been fixed.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 11:00 AM UTC
- Resolved
- Jul 24, 2026, 11:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 24, 2026, 03:59 PM UTC
Some customers may have experienced delays in alert notifications from 4 am ~ 6 am (PST), 2026. Datapoint ingest is not affected. The issue is recovered.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 12:20 PM UTC
- Resolved
- Jul 15, 2026, 04:00 PM UTC
- Duration
- 3h 39m
Affected: Splunk Observability Cloud APIAlerting
Timeline · 4 updates
-
investigating Jul 15, 2026, 12:20 PM UTC
We are currently investigating the issue. Certain APIs may be failing and active alert pages is loading slowly. No data is being dropped or lost.
-
identified Jul 15, 2026, 12:48 PM UTC
The issue has been identified and the fix is being implemented.
-
monitoring Jul 15, 2026, 02:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 15, 2026, 04:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2026, 12:03 PM UTC
- Resolved
- Jul 11, 2026, 06:09 PM UTC
- Duration
- 1d 6h
Affected: Alerting
Timeline · 20 updates
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 11:45 PM UTC
- Resolved
- Jul 08, 2026, 11:45 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 09, 2026, 02:36 AM UTC
Between 4:45p - 6:45p PDT a very small percentage of metric data points were being dropped. This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 09:47 PM UTC
- Resolved
- Jul 08, 2026, 11:52 PM UTC
- Duration
- 2h 5m
Affected: Datapoint Ingest
Timeline · 5 updates
-
investigating Jul 08, 2026, 09:47 PM UTC
Starting at 11:30a PDT, datapoint ingest is affected and we are dropping a small percentage of datapoints. We are investigating and will provide an update as progress is made.
-
investigating Jul 08, 2026, 10:35 PM UTC
We continue to investigate the issue affecting a small percentage of datapoint ingest in US0. Our engineering teams are actively working on the issue and evaluating potential mitigations. We will provide another update as more information becomes available.
-
investigating Jul 08, 2026, 11:29 PM UTC
We continue to investigate the issue affecting a small percentage of datapoint ingest in US0. Our engineering teams are actively working on the issue. We will provide another update as more information becomes available.
-
monitoring Jul 08, 2026, 11:33 PM UTC
We have observed improvement in datapoint ingest in US0, and the rate of dropped datapoints has returned to expected levels. We are continuing to monitor the service closely to ensure stability. We will provide another update once monitoring is complete or if any additional issues are observed.
-
resolved Jul 08, 2026, 11:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 02:21 PM UTC
- Resolved
- Jul 08, 2026, 03:33 PM UTC
- Duration
- 1h 11m
Affected: Splunk Synthetics Monitoring InterfaceSplunk AlwaysOn Profiling Interface
Timeline · 4 updates
-
investigating Jul 08, 2026, 02:21 PM UTC
Starting at 6:48a PDT, Synthetic test runs are not able to be viewed in the user interface. Tests are still running and detectors are still working. We are investigating the issue and will send updates as progress is made.
-
investigating Jul 08, 2026, 02:43 PM UTC
The APM Profiling user interface is also unavailable at this time due to the same underlying issue. We are continuing to investigate and will provide updates as progress is made.
-
investigating Jul 08, 2026, 03:05 PM UTC
The data visible in the APM Profiling user interface is experiencing delays. Splunk Synthetics Monitoring is operational. We are continuing to investigate and will provide updates as progress is made.
-
resolved Jul 08, 2026, 03:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2026, 05:00 AM UTC
- Resolved
- Jul 08, 2026, 05:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 08, 2026, 10:51 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.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2026, 12:47 AM UTC
- Resolved
- Jul 03, 2026, 02:47 AM UTC
- Duration
- 2h
Affected: Splunk APM Trace DataSplunk RUM Session Details
Timeline · 5 updates
-
investigating Jul 03, 2026, 12:47 AM UTC
We are investigating a partial outage of the Splunk RUM Session Detail feature. Session data ingest is not impacted at this time. We will provide an update as soon as possible.
-
investigating Jul 03, 2026, 01:10 AM UTC
We are continuing to investigate this issue.
-
investigating Jul 03, 2026, 01:53 AM UTC
We are continuing to investigate this issue.
-
identified Jul 03, 2026, 02:04 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jul 03, 2026, 02:47 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 08:55 PM UTC
- Resolved
- Jul 02, 2026, 10:35 PM UTC
- Duration
- 1h 39m
Affected: Splunk Observability Cloud Web InterfaceAlerting
Timeline · 3 updates
-
investigating Jul 02, 2026, 08:55 PM UTC
Customers may be experiencing delays in some detectors. Datapoint ingest is not affected. We are investigating and will provide an update shortly.
-
identified Jul 02, 2026, 09:36 PM UTC
We have identified the source of the issue and have taken mitigation actions. Recovery is in progress, and we are seeing gradual improvement. Our teams are continuing to investigate the underlying cause while monitoring the recovery. We will provide another update as more information becomes available.
-
resolved Jul 02, 2026, 10:35 PM UTC
The issue causing delays in some detectors has been resolved. Systems have recovered, and detector processing has returned to expected levels. Thank you for your patience while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2026, 07:21 PM UTC
- Resolved
- Jul 02, 2026, 09:31 PM UTC
- Duration
- 2h 9m
Affected: Splunk APM InterfaceSplunk APM Monitoring MetricSets
Timeline · 4 updates
-
investigating Jul 02, 2026, 07:21 PM UTC
A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be delayed by more than five minutes. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.
-
investigating Jul 02, 2026, 08:16 PM UTC
We are continuing to investigate this issue.
-
monitoring Jul 02, 2026, 08:44 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 02, 2026, 09:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2026, 12:00 PM UTC
- Resolved
- Jul 01, 2026, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 01, 2026, 02:18 PM UTC
We are investigating a partial outage of the Splunk APM Tag Spotlight. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 12:00 PM UTC
- Resolved
- Jun 25, 2026, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 26, 2026, 07:36 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
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 03:37 PM UTC
- Resolved
- Jun 17, 2026, 09:09 PM UTC
- Duration
- 5h 32m
Affected: Splunk APM Trace Data
Timeline · 6 updates
-
investigating Jun 17, 2026, 03:37 PM UTC
We are investigating why Trace Lookups are failing for traces created between approximately 5:30am PT - 7:30am PT. Monitoring MetricSets and Troubleshooting MetricSets are not impacted. Metrics are still available. We are investigating the issue.
-
investigating Jun 17, 2026, 04:43 PM UTC
We are still investigating the issue.
-
investigating Jun 17, 2026, 05:56 PM UTC
We are continuing to investigate this issue.
-
identified Jun 17, 2026, 06:35 PM UTC
The issue affecting Trace Lookup searchability for traces generated between approximately 5:30 AM and 7:30 AM PT on June 17 has been identified. This occurred during an approved maintenance window associated with repartitioning and scaling activities. Customers may be unable to search for traces generated during this timeframe. Trace ingestion and processing are operating normally, and traces generated outside of the affected window remain searchable. Our team has developed a fix and is currently validating it through internal testing. We expect validation to complete within approximately two hours and will provide another update once the fix is ready for deployment or as additional information becomes available.
-
identified Jun 17, 2026, 08:07 PM UTC
We continue to make progress toward resolution. The fix is currently moving through the implementation process and will be rolled out once all deployment steps have been completed. We will provide another update as progress continues.
-
resolved Jun 17, 2026, 09:09 PM UTC
The fix has been successfully deployed, and we have confirmed that the issue affecting Trace Lookup searchability for traces generated between approximately 5:30 AM and 7:30 AM PT on June 17 has been resolved. Customers should now be able to search affected traces as expected.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 03:07 PM UTC
- Resolved
- Jun 17, 2026, 03:33 PM UTC
- Duration
- 26m
Affected: Splunk APM Monitoring MetricSetsSplunk APM Trace DataSplunk APM Tag SpotlightSplunk APM Business WorkflowsExtended trace retention
Timeline · 2 updates
-
monitoring Jun 17, 2026, 03:07 PM UTC
The Scheduled Maintenance for US0 Splunk APM Span Firehose Optimization has been extended while we continue to monitor the improvements.
-
resolved Jun 17, 2026, 03:33 PM UTC
We have completed our Scheduled Maintenance window. Thanks for your patience.
Read the full incident report →
