We started checking Splunk on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Splunk reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Splunk's own status page declared. Below it, any public chatter we saw about Splunk and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Splunk's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Splunk in the last 24 hours, which is not evidence that nothing is wrong.
Splunk's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Splunk's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Splunk next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
440
US-West
100.00%
337
Europe
100.00%
309
Asia-Pacific
100.00%
187
Their declared record
Splunk's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Splunkbase is DownMajor outage
Jul 31, 2026, 12:34 AM UTC to Jul 31, 2026, 1:22 AM UTC (48 min)resolved
their latest update (Jul 31, 2026, 1:22 AM UTC): Splunk has resolved the issue affecting Splunkbase at splunkbase.splunk.com.
Users should now be able to access Splunkbase, download apps, and install apps in Splunk Cloud through the UI as expected.
We apologize for the disruption and appreciate your patience while we worked to …
Expected Restart(s) Following Maintenance ActivityMinor incident
May 29, 2026, 9:35 PM UTC to Jun 1, 2026, 3:04 AM UTC (2d 5h)resolved
their latest update (Jun 1, 2026, 3:04 AM UTC): This incident has been resolved.
DNS synchronization issue affecting HEC dash DNS records | #cinc-66607_cloud_multiple(Degraded Performance)Minor incident
May 28, 2026, 6:22 AM UTC to May 28, 2026, 7:21 AM UTC (1h)resolved
their latest update (May 28, 2026, 7:21 AM UTC): Some customers experienced traditional HEC ingestion issues due to a DNS synchronization issue affecting HEC dash DNS records using the format http-inputs-${stack}.splunkcloud.com.
HEC ingestion using the current dot-format DNS records, http-inputs.${stack}.splunkcloud.com, is fu…
AWS Privatelink unable to receive HEC data with multiple AWS regions impacted | #cinc-66607_cloud_multiple_privatelink (Major Outage)Minor incident
May 28, 2026, 1:31 AM UTC to May 28, 2026, 1:43 AM UTC (12 min)resolved
their latest update (May 28, 2026, 1:43 AM UTC): The incident has been resolved. Our investigation determined that an internal configuration change began impacting service at 20:34 UTC on May 27, 2026. A fix was developed and rolled out beginning at 23:45 UTC, with full remediation completed by 03:45 UTC on May 28, 2026.
We apo…
Cloud Region Network Connectivity Impact | CINC-66292 (Major Outage)Minor incident
May 8, 2026, 1:53 AM UTC to May 10, 2026, 3:29 PM UTC (2d 13h)resolved
their latest update (May 10, 2026, 3:29 PM UTC): This issue has been resolved.
Teams will now begin their root cause analysis. If you believe that you are still impacted by this issue please <a href="https://www.splunk.com/en_us/about-splunk/contact-us.html#customer-support">contact customer support</a> and reference CINC-66…
May 4, 2026, 6:19 PM UTC to May 4, 2026, 8:41 PM UTC (2h 22m)resolved
their latest update (May 4, 2026, 8:41 PM UTC): This incident has been resolved.
Internal IT issue (Major Outage)All systems operational
May 2, 2026, 1:44 AM UTC to May 2, 2026, 8:01 AM UTC (6h 17m)resolved
their latest update (May 2, 2026, 8:01 AM UTC): This incident has been resolved.
Service Advisory: KVservice issues impacting Enterprise Security search performancePartial outage
Apr 9, 2026, 1:04 AM UTC to Apr 9, 2026, 1:25 AM UTC (21 min)resolved
their latest update (Apr 9, 2026, 1:25 AM UTC): Our engineering team has successfully implemented the fix for the KVservice issue. We have monitored the environment and can confirm that there are no recurring errors.
All searches and dashboards within the Enterprise Security (ES) application are now fully operational.
If you…
Mar 3, 2026, 6:07 PM UTC to Mar 25, 2026, 5:27 PM UTC (21d 23h)resolved
their latest update (Mar 25, 2026, 5:27 PM UTC): Cisco has confirmed that the impact of the cloud service provider outage in the Middle East has been mitigated. Cisco engineers have successfully transitioned affected services out of the region.
We have identified all affected customers and will be reaching out to each of you i…
Multiple Services OutageMajor outage
Nov 18, 2025, 12:52 PM UTC to Nov 18, 2025, 9:52 PM UTC (9h)resolved
their latest update (Nov 18, 2025, 9:52 PM UTC): All impacted services have been fully remediated. Systems are operating normally, and no further impact is expected. We will continue to monitor to ensure full service stability. Thank you for your patience throughout this incident.
Showing the 10 most recent of 35 incidents Splunk has declared in the history we hold.
These entries are Splunk's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Splunk's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.