Splunk Cloud Platform Status

Splunk Cloud Platform

All Systems Operational

About This Site

This page published on May 15, 2023, will list widespread multi-customer outages in Splunk Cloud Platform from this day onwards. In times of customer-specific outages in Splunk Cloud Platform, customer will continue to receive notifications via other established mechanisms. The page is not intended to replace our customer support offering or other offerings we have in place to enlighten our customers on their specific Splunk instances.

Ingest Operational

Search Operational

Index Operational

Infrastructure Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Jun 12, 2025

No incidents reported today.

Jun 11, 2025

No incidents reported.

Jun 10, 2025

No incidents reported.

Jun 9, 2025

No incidents reported.

Jun 8, 2025

No incidents reported.

Jun 7, 2025

<SOAR Playbooks can't be saved> | <CINC-61144> (Major Outage)

Resolved - 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 contact customer support and reference .
Jun 7, 01:22 UTC

Monitoring - We have implemented a fix for this issue. During this time we are monitoring the results to confirm the resolution and will continue to provide any additional updates once available.
Jun 6, 21:21 UTC

Identified - Splunk is aware of an issue currently affecting SOAR customers. As a result of the issue, users will not be able to save playbooks after making edits. Error message: "Unexpected keyword argument 'code_names' in function call"

We understand the impact this has on your operations and are working to resolve the issue as quickly as possible. We will provide more information when it becomes available. No actions are needed from customers at this time.

Thank you for your patience and understanding.
Jun 5, 19:14 UTC

Jun 6, 2025

Jun 5, 2025

Jun 4, 2025

No incidents reported.

Jun 3, 2025

<SOAR Playbooks being disabled> | <CINC-61075> (Degraded Performance)

Resolved - This fix will be deployed to all cloud stacks on Thursday, June 5, 2025, between 1:00 AM and 3:00 AM local stack time.
On-premises customers will receive the updated release for download on June 5, 2025 (PDT).

If you wish to apply the workaround before the scheduled fix is deployed, you can do so by following the steps below:
- Open the affected playbook in the Visual Playbook Editor (VPE).
- Manually review and adjust the join settings (check/uncheck as needed).
- Save the playbook to apply the changes.

Teams will now begin their root cause analysis. If you believe that you are still impacted by this issue please contact customer support and reference CINC-61075.
Jun 3, 22:02 UTC

Update - Splunk has identified an issue in SOAR version 6.4.1 where Playbooks may appear to load correctly but failing in backend execution.
A fix is in progress, and no immediate action is required from customers.

As a workaround, to mitigate the impact:

- Open the playbook in the Visual Playbook Editor (VPE)

- Manually review and adjust the join settings (check/uncheck as needed)

- Save the playbook to apply the changes

We appreciate your patience and will share further updates as the fix is implemented.
May 31, 06:35 UTC

Identified - Hello,

Splunk Cloud customers using the SOAR platform may be impacted by Playbooks appearing to load but backend logic failing.

We have identified the source of the issue in version 6.4.1 and are currently working on implementing a fix. At this time, there is no further action needed from customers.

There is an active workaround to mitigate impact:

- Open the playbook in the Visual Playbook Editor (VPE).
- Manually review and adjust the join settings (check/uncheck as needed).
- Save the playbook to apply the changes

Your patience is greatly appreciated and we will provide more updates as we implement the fix.
May 30, 22:52 UTC

Jun 2, 2025

No incidents reported.

Jun 1, 2025

No incidents reported.

May 31, 2025

May 30, 2025

May 29, 2025

No incidents reported.