Cronologia delle interruzioni di Splunk

1. 31 luglio 2026 alle ore 00:34 UTCinvestigating

   Splunk sta indagando su un problema che attualmente interessa Splunkbase a "splunkbase.splunk.com". Di conseguenza, gli utenti potrebbero non essere in grado di accedere a Splunkbase e possono ricevere un errore "500". Gli utenti potrebbero anche non essere in grado di scaricare applicazioni o installare applicazioni in Splunk Cloud attraverso l'interfaccia utente. Comprendiamo l'impatto che questo può avere sulle vostre operazioni e stiamo lavorando per risolvere il problema. Forniamo un altro aggiornamento in 1 ora, o prima se ulteriori informazioni diventano disponibili.

2. 31 luglio 2026 alle ore 00:35 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 31 luglio 2026 alle ore 01:22 UTCresolved

   Splunk ha risolto il problema che interessa Splunkbase a splunkbase.splunk.com. Gli utenti dovrebbero ora essere in grado di accedere a Splunkbase, scaricare applicazioni e installare applicazioni in Splunk Cloud attraverso l'interfaccia utente come previsto. Ci scusiamo per la rottura e apprezziamo la vostra pazienza mentre abbiamo lavorato per ripristinare il servizio.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 29 maggio 2026 alle ore 21:35 UTCinvestigating

   As part of a recent maintenance activity, some environments with ITSI may experience a rolling restart of the environment. Customers may temporarily see restart notifications or reload prompts within the UI while these activities complete.

2. 29 maggio 2026 alle ore 22:14 UTCinvestigating

   Update: Rolling restart activities may be occurring at midnight local time for the applicable cloud provider region for some environments with ITSI. Customers may continue to observe restart notifications or reload prompts within the UI while these activities complete. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required.

3. 30 maggio 2026 alle ore 06:56 UTCmonitoring

   We have identified the cause of the rolling restart activity affecting some environments with ITSI and continue to monitor impacted environments. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. To provide a more controlled customer experience, remaining restart activities are being coordinated to occur at midnight local time for the applicable cloud provider region. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required.

4. 31 maggio 2026 alle ore 03:22 UTCmonitoring

   We continue to monitor the rolling restart activities affecting some environments with ITSI. Communications have been sent to customers whose environments may experience potential impact. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. Remaining restart activities continue to be coordinated for midnight local time in the applicable cloud provider region to provide a more controlled customer experience. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required.

5. 1 giugno 2026 alle ore 03:04 UTCresolved

   This incident has been resolved.

1. 28 maggio 2026 alle ore 06:22 UTCidentified

   Some customers are experiencing 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 functioning correctly. As a mitigation, customers using the dash-format HEC endpoint should update their upstream systems to use the dot-format endpoint: http-inputs.${stack}.splunkcloud.com. Our engineering teams are working to restore the affected DNS records through Zone DNS synchronization. We will provide another update once DNS synchronization has completed or if there is a meaningful change in impact.

2. 28 maggio 2026 alle ore 07:21 UTCresolved

   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 functioning correctly. This issue was resolved for affected customers by 07:00 UTC.

1. 28 maggio 2026 alle ore 00:15 UTCidentified

   We’re investigating an issue affecting some customers hosted in ap-northeast-1, eu-central-1, and us-east-1. Impacted Splunk Cloud Platform customers in these regions may experience access issues. Our teams are actively working to restore service, and we’ll share updates as more information becomes available

2. 28 maggio 2026 alle ore 01:27 UTCmonitoring

   A mitigation has been successfully applied across the fleet. Engineering teams are actively monitoring to confirm service has been fully restored and to ensure no further interruptions occur.

3. 28 maggio 2026 alle ore 01:31 UTCidentified

   We identified an issue caused by an internal change on May 26, 2026, that impacted ingestion through a PrivateLink. A fix has been identified, released and is currently rolling out. Some customers may continue to experience impact while the fix is being applied. We’ll provide another update once rollout is complete. Our teams are actively working to restore service and will provide another update as soon as more information is available

4. 28 maggio 2026 alle ore 01:41 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 28 maggio 2026 alle ore 01:43 UTCresolved

   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 apologise for any inconvenience this caused and appreciate your patience while our teams worked to restore service.

1. 8 maggio 2026 alle ore 01:53 UTCinvestigating

   We are investigating an issue indicating one of our suppliers experiencing in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.

2. 8 maggio 2026 alle ore 03:01 UTCinvestigating

   We are investigating an issue indicating one of our suppliers experiencing outage in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.

3. 8 maggio 2026 alle ore 03:28 UTCinvestigating

   We continue to investigate an issue indicating one of our suppliers experiencing in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for limited number of customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.

4. 8 maggio 2026 alle ore 04:26 UTCinvestigating

   As teams continue to investigate we will tentatively provide our next update by 05:00 AM UTC, or sooner if new information becomes available.

5. 8 maggio 2026 alle ore 05:35 UTCinvestigating

   Investigation is in progress, we will provide our next update by 07:00 AM UTC, or sooner if new information becomes available.

6. 8 maggio 2026 alle ore 06:49 UTCinvestigating

   Investigation is in progress, we will provide our next update by 09:00 AM UTC, or sooner if new information becomes available.

7. 8 maggio 2026 alle ore 09:03 UTCinvestigating

   Investigation is ongoing, and remediation efforts are in progress. We will provide our next update by 10:00 UTC, or sooner if new information becomes available.

8. 8 maggio 2026 alle ore 09:59 UTCinvestigating

   Investigation is ongoing, and remediation efforts are in progress. We will provide our next update by 11:00 UTC, or sooner if new information becomes available.

9. 8 maggio 2026 alle ore 11:30 UTCinvestigating

   Investigation remains ongoing, and we continue to make progress toward recovery. Some affected infrastructure has stabilized, but some customers may still experience impact while remediation continues. Based on current recovery efforts, full restoration is expected to take several more hours. We will provide our next update by 13:00 UTC, or sooner if new information becomes available.

10. 8 maggio 2026 alle ore 13:29 UTCinvestigating

    Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 15:00 UTC, or sooner if new information becomes available.

11. 8 maggio 2026 alle ore 14:21 UTCinvestigating

    Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 17:00 UTC, or sooner if new information becomes available.

12. 8 maggio 2026 alle ore 16:42 UTCinvestigating

    Update still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 19:00 UTC, or sooner if new information becomes available.

13. 8 maggio 2026 alle ore 19:01 UTCinvestigating

    We are still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 21:00 UTC, or sooner if new information becomes available.

14. 8 maggio 2026 alle ore 21:15 UTCinvestigating

    We are still investigating and recovery efforts remain in progress. Some impacted environments have shown improvement, but some customers may continue to experience service impact while remediation and validation continue. We will provide our next update by 23:00 UTC, or sooner if new information becomes available.

15. 8 maggio 2026 alle ore 23:15 UTCinvestigating

    Service restoration is progressing steadily following the implementation of our mitigation efforts. While most environments have recovered, some customers may still experience intermittent impact as we finalize remediation and validation. Our team is actively monitoring all systems to ensure full stability.

16. 9 maggio 2026 alle ore 06:57 UTCidentified

    Service restoration is progressing steadily following the implementation of our mitigation efforts. While most environments have recovered, some customers may still experience intermittent impact as we finalize remediation and validation. Our team is actively monitoring all systems to ensure full stability.

17. 9 maggio 2026 alle ore 14:46 UTCidentified

    Recovery continues following mitigation efforts. Most environments have recovered, though some customers may still experience intermittent impact while final remediation and validation are completed. Our team is actively monitoring to confirm full stability.

18. 10 maggio 2026 alle ore 01:04 UTCidentified

    Recovery continues to progress following our mitigation efforts. Most environments are operating normally, and we’re seeing stable performance across the majority of systems. A small number of customers may still experience intermittent impact as we complete final remediation and validation. Our team remains actively engaged and monitoring closely to confirm full stability.

19. 10 maggio 2026 alle ore 15:29 UTCresolved

    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 CINC-66292.

1. 4 maggio 2026 alle ore 18:19 UTCidentified

   We are currently addressing a major service disruption affecting search performance, which began at 16:34 UTC. Users may experience degraded search performance and intermittent UI errors. Our engineering teams have identified the root cause and are actively working to deploy a resolution. We are monitoring the situation closely and will provide further updates as they become available.

2. 4 maggio 2026 alle ore 18:49 UTCidentified

   We are observing service recovery for the majority of our customers. Our engineering teams are actively investigating and addressing the remaining isolated cases where service has not yet been fully restored. We will continue to monitor the environment closely until all services are operating at normal capacity.

3. 4 maggio 2026 alle ore 19:09 UTCmonitoring

   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.

4. 4 maggio 2026 alle ore 19:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 4 maggio 2026 alle ore 20:04 UTCmonitoring

   We are continuing to monitor the restoration of services for the majority of our impacted customers. Our teams are working diligently to resolve remaining issues for any users who have not yet seen a full return to normal service. We will continue to monitor the environment closely until all services are fully operational.

6. 4 maggio 2026 alle ore 20:41 UTCresolved

   This incident has been resolved.

1. 2 maggio 2026 alle ore 01:44 UTCinvestigating

   We are currently experiencing an internal IT service disruption. As a result all planned maintenance activities scheduled are being paused/canceled and we will provide further updates as more information becomes available.

2. 2 maggio 2026 alle ore 03:01 UTCmonitoring

   The issue is currently stable, and teams are continuing to monitor service behaviour closely. We will continue to provide updates until the issue is fully resolved.

3. 2 maggio 2026 alle ore 08:01 UTCresolved

   This incident has been resolved.

1. 9 aprile 2026 alle ore 00:10 UTCinvestigating

   Our engineering team has identified an issue with the KVservice that is currently impacting search performance for ad-hoc, saved, and scheduled searches. Additional symptoms may include, but not limited to: - Inability to save searches within the Enterprise Security (ES) application. - Errors when attempting to update application settings, such as credentials. This is an active investigation. We are working to resolve this as quickly as possible and will provide status updates as more information becomes available. We apologize for any inconvenience this may cause.

2. 9 aprile 2026 alle ore 01:04 UTCidentified

   Our engineering teams have narrowed the scope of the issue: Any search utilizing the KV Services were failing. This impact extended to the Mission Control and Analyst Queue dashboards. Additionally, we have identified the root cause and are actively mitigating the impact. Once mitigation is complete, we will continue to monitor the environment to ensure service stability for all users. We will continue to provide status updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

3. 9 aprile 2026 alle ore 01:25 UTCresolved

   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 continue to experience any issues related to this incident, please contact us by submitting a support case. We apologize for the inconvenience this may have caused and appreciate your patience as we worked to restore service.

1. 11 marzo 2026 alle ore 15:45 UTCidentified

   Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, Login, Search and Ingest may be impacted for customers in the affected region. Cisco and Splunk are exploring what options are available for affected customers and will contact those affected customers directly. We will continue to closely monitor this issue as it unfolds.

2. 25 marzo 2026 alle ore 17:27 UTCresolved

   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 individually to discuss specific next steps and any necessary remediation. A proactive support case has been opened on your behalf to coordinate this effort. If you have any immediate concerns, please reach out to your account team or simply reply to your support case. Cisco appreciates your patience and cooperation on this matter.

1. 18 novembre 2025 alle ore 12:52 UTCinvestigating

   We are currently experiencing a KVService outage impacting services. Our teams are actively working to resolve the issue. We will provide an update within the next 60 minutes.

2. 18 novembre 2025 alle ore 14:01 UTCinvestigating

   We are currently experiencing a global outage impacting multiple Splunk services including Vault, KVService, Identity and Access Control (IAC), Splunk Mobile app, VictorOps, and Ingest processor, Edge processor. Customers may experience service disruptions such as login failures, lookup access issues, and degraded performance. We acknowledge the impact and are actively working with our partners to restore full service.

3. 18 novembre 2025 alle ore 15:30 UTCinvestigating

   We are still investigating the issue. Customers may experience service disruptions such as login failures, lookup access issues, and degraded performance. We acknowledge the impact and are actively working with our partners to restore full service.

4. 18 novembre 2025 alle ore 16:34 UTCmonitoring

   Splunk continues to monitor and remediate the services affected by this issue. Several services remain impacted; however, they are currently in a recovering state. We do not have an ETA for full recovery at this time, but our teams are working to restore services as quickly as possible. We appreciate your continued patience.

5. 18 novembre 2025 alle ore 17:27 UTCmonitoring

   Several Splunk services are still in a recovering state. Our teams continue to monitor progress and work through remaining backlogs to fully restore functionality. We will provide further updates as recovery advances.

6. 18 novembre 2025 alle ore 18:24 UTCmonitoring

   All impacted Splunk services are back up, with a few still in recovery and monitoring. Our teams continue to work through remaining backlogs and validate full functionality across all components.

7. 18 novembre 2025 alle ore 21:20 UTCmonitoring

   All impacted Splunk services are back up, with Ingest Processor still in recovery and monitoring. Our teams continue to work through remaining backlogs and validate full functionality across all components.

8. 18 novembre 2025 alle ore 21:52 UTCresolved

   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.

1. 13 novembre 2025 alle ore 05:20 UTCinvestigating

   We are currently investigating the issue with ACS (Admin Config Service) requests causing failures for all Splunk Cloud Platform customers, resulting in the error message "service temporarily unavailable, please try again later" when accessing self-service operations.

2. 13 novembre 2025 alle ore 05:49 UTCinvestigating

   Our teams are currently investigating the issue with ACS (Admin Config Service) requests causing failures for all Splunk Cloud Platform customers, resulting in the error message "service temporarily unavailable, please try again later" when accessing self-service operations.

3. 13 novembre 2025 alle ore 07:17 UTCidentified

   This issue has been identified and fix is being implemented.

4. 13 novembre 2025 alle ore 08:21 UTCidentified

   The issue affecting ACS has been identified. Our team is currently testing a potential fix to ensure it resolves the problem. Service functionality may remain limited during this time. We will provide updates as testing progresses.

5. 13 novembre 2025 alle ore 09:34 UTCidentified

   The issue affecting ACS has been identified. Our team is continuing testing a potential fix to ensure it resolves the problem. Service functionality may remain limited during this time. We will provide updates as testing progresses.

6. 13 novembre 2025 alle ore 10:15 UTCmonitoring

   We have identified the root cause of the earlier disruption and applied a workaround to restore full functionality. All ACS services are now operating normally, and our monitoring indicates requests are being processed successfully. We will implement a permanent fix during a scheduled maintenance window, and no customer impact is expected during that time. Thank you for your patience as we worked to resolve this issue.

7. 13 novembre 2025 alle ore 14:21 UTCresolved

   All ACS services are now operating normally, and our monitoring indicates requests are being processed successfully. We will implement a permanent fix during a scheduled maintenance window, and no customer impact is expected during that time. Thank you for your patience as we worked to resolve this issue.

1. 4 novembre 2025 alle ore 17:42 UTCinvestigating

   We are aware that some customers are currently experiencing issues logging in to the Splunk Cloud Platform. Our technical teams are actively engaged and investigating the root cause. We are working to resolve this as quickly as possible and will provide further updates as more information becomes available.

2. 4 novembre 2025 alle ore 18:41 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 novembre 2025 alle ore 18:59 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 4 novembre 2025 alle ore 19:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 4 novembre 2025 alle ore 20:21 UTCresolved

   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 CINC-63161.

1. 24 ottobre 2025 alle ore 15:42 UTCinvestigating

   We are investigating a potential issue with KVService, that may impact several Splunk cloud platform customers in eu-central-1. As a result of this issue, customers are experiencing lookups failing to complete. We will provide an update within the next 30 minutes.

2. 24 ottobre 2025 alle ore 16:40 UTCinvestigating

   We continue to investigate the issue with KVService, that may impact several Splunk cloud platform customers in eu-central-1. As a result of this issue, customers are experiencing lookups failing to complete as well as errors within Splunk applications that depend heavily on KVService.

3. 24 ottobre 2025 alle ore 17:30 UTCinvestigating

   We are continuing to investigate this issue.

4. 24 ottobre 2025 alle ore 18:01 UTCidentified

   The issue has been identified and a temporary fix is implemented.

5. 24 ottobre 2025 alle ore 18:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

6. 25 ottobre 2025 alle ore 07:00 UTCresolved

   This incident has been resolved after applying the fix.

1. 20 ottobre 2025 alle ore 10:24 UTCidentified

   We are investigating an issue indicating an AWS outage in us-east-1. As a result, the Splunk Cloud Platform environment may be inaccessible for customers in the specified region. Our teams are working with the provider to resolve this issue. Your patience is greatly appreciated and we will provide more updates upon resolution.

2. 20 ottobre 2025 alle ore 11:44 UTCidentified

   We are continuing to work with service provider on a fix for this issue.

3. 20 ottobre 2025 alle ore 13:06 UTCmonitoring

   We are aware of recent issues impacting our services due to an AWS incident in the US-EAST-1 region. AWS has applied mitigations and is making progress toward full resolution. At this time, our systems are stable, and we are closely monitoring for any further impact. We will continue to monitor the situation and provide another update by 7:00 AM PDT or sooner if new information becomes available.

4. 20 ottobre 2025 alle ore 15:02 UTCmonitoring

   We have confirmed that multiple AWS services experienced network connectivity issues in the US-EAST-1 Region. We are seeing early signs of recovery for these connectivity issues and AWS is continuing to investigate the root cause. AWS has applied mitigations and is making progress toward full resolution. Thank you for your patience.

5. 20 ottobre 2025 alle ore 15:55 UTCidentified

   We are aware of an outage impacting multiple AWS services in the US-EAST-1 region. This is affecting several Splunk Cloud Platform environments that rely on these AWS services. Splunk users may experience delays or errors in search execution, data ingestion, or app functionality for stacks hosted in the affected AWS region (US-EAST-1). According to AWS, they have narrowed down the source of the network connectivity issues to an internal subsystem responsible for monitoring the health of their network load balancers. AWS has implemented throttling for new EC2 instance launches to aid recovery and is actively applying mitigations. https://health.aws.amazon.com/health/status?path=open-issues Splunk is continuing to monitor the situation closely and will provide updates as AWS progresses toward full service restoration.

6. 20 ottobre 2025 alle ore 17:12 UTCidentified

   We continue to track the ongoing AWS operational issue in the US-EAST-1 (N. Virginia) region that is causing intermittent service degradation across multiple AWS services. This outage continues to affect several Splunk Cloud Platform environments hosted in the impacted region. Customers hosted in US-EAST-1 may continue to experience latency, delayed search results, or reduced availability of certain Cloud functions. All other Splunk Cloud regions remain fully operational. https://health.aws.amazon.com/health/status?path=open-issues Splunk is continuing to monitor the situation closely and will provide updates as AWS progresses toward full service restoration.

7. 20 ottobre 2025 alle ore 18:41 UTCidentified

   Splunk is actively monitoring an ongoing operational issue in the AWS US-EAST-1 (N. Virginia) region that is causing intermittent service degradation across multiple AWS services and impacting several Splunk Cloud Platform environments. While steady recovery is being observed across Splunk's cloud infrastructure, customers hosted in US-EAST-1 may still experience latency, delayed search results, or reduced availability of certain Cloud functions until AWS infrastructure fully recovers. All other Splunk Cloud regions remain fully operational. Splunk will continue to provide updates as AWS progresses toward full service restoration.

8. 20 ottobre 2025 alle ore 20:10 UTCidentified

   As AWS continues its recovery efforts in the US-EAST-1 region, Splunk Cloud Platform customers in this region may still experience intermittent issues. We are closely monitoring AWS updates and will provide additional status information as it becomes available. All other Splunk Cloud regions remain fully operational.

9. 20 ottobre 2025 alle ore 22:13 UTCmonitoring

   As AWS continues its recovery efforts in the US-EAST-1 region, Splunk Cloud Platform customers in this region may still experience intermittent issues. We are closely monitoring AWS updates and will provide additional status information as it becomes available. All other Splunk Cloud regions remain fully operational.

10. 20 ottobre 2025 alle ore 23:09 UTCmonitoring

    We are continuing to monitor for any further issues.

11. 20 ottobre 2025 alle ore 23:10 UTCmonitoring

    AWS has reported that the earlier issues impacting services in the US-EAST-1 (N. Virginia) region have been fully resolved as of 3:01 PM PDT. All impacted services have returned to normal operations. Users may continue to observe minor latency or delays as AWS and dependent services complete backlog processing and return to standard performance levels. We are closely monitoring our systems and will provide further updates if any new issues arise. Thank you for your patience.

12. 20 ottobre 2025 alle ore 23:22 UTCresolved

    AWS has reported that the earlier issues impacting services in the US-EAST-1 (N. Virginia) region have been fully resolved as of 3:01 PM PDT. All impacted services have returned to normal operations. Users may continue to observe minor latency or delays as AWS and dependent services complete backlog processing and return to standard performance levels. We understand the criticality of your services and appreciate your patience.

1. 22 settembre 2025 alle ore 10:15 UTCinvestigating

   We have identified an issue with the Splunk Mobile app not being able to connect to Splunk Secure Gateway. This issue ONLY affects the mobile apps, and not customer's Splunk Enterprise/Splunk Cloud instances. Your patience is greatly appreciated and we will provide more updates as we investigate and work on a fix for the issue.

2. 22 settembre 2025 alle ore 12:06 UTCidentified

   The issue has been identified and a fix is being implemented. Please note that the issue ONLY affects the Splunk mobile app, and not customer's Splunk Enterprise/Splunk Cloud instances.

3. 22 settembre 2025 alle ore 14:58 UTCidentified

   A fix has been identified and is being currently implemented. Please note that the issue ONLY affects the Splunk mobile app, and not customer's Splunk Enterprise/Splunk Cloud instances.

4. 22 settembre 2025 alle ore 19:09 UTCresolved

   A software fix has been provided for release to consumers. iOS version 2.44.0 is ready and available for customer download via the App Store. Android version 2.43.1 is awaiting review and will be released in the upcoming days. Affected customers should update to the fixed app version as soon as it is available. Please note that the issue ONLY affects the Splunk mobile app, not customers' Splunk Enterprise/Splunk Cloud instances.

1. 19 agosto 2025 alle ore 16:56 UTCinvestigating

   We are investigating a potential issue with search and ingest that may impact customers on Splunk Cloud Platform for FedRAMP High and Splunk Cloud Platform for IL5. As a result of the issue, customer search and indexing may experience issues completing successfully. We will provide an update within the next 30 minutes.

2. 19 agosto 2025 alle ore 17:25 UTCidentified

   We have identified the source of the issue and are currently working on implementing a fix.

3. 19 agosto 2025 alle ore 18:26 UTCidentified

   We are starting to see recovery on some of the impacted instances. Teams continue to work on implementing a fix for this issue.

4. 19 agosto 2025 alle ore 18:54 UTCidentified

   We see recovery on some of the impacted instances. Teams continue to work on implementing a fix for this issue.

5. 19 agosto 2025 alle ore 21:49 UTCidentified

   We continue working to implement a fix for this issue.

6. 19 agosto 2025 alle ore 21:56 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

7. 19 agosto 2025 alle ore 23:00 UTCmonitoring

   We are continuing to monitor for any further issues.

8. 19 agosto 2025 alle ore 23:01 UTCresolved

   This incident has been resolved.

1. 17 giugno 2025 alle ore 20:31 UTCresolved

   We are aware of a service provider outage on GitHub that lasted from 12:42 PM PT to 1:22 PM PT. As a result, changes such as firewall rule modifications or updates to the IP allow list made via the Admin Config Service (ACS) may have failed during this time. Further details may be found at https://www.githubstatus.com This issue has been resolved by the provider. If you believe that you are still impacted by this issue please contact customer support and reference CINC-61287.

1. 12 giugno 2025 alle ore 19:52 UTCidentified

   We are investigating a reported issue for all stacks hosted on GCP. As a result, the Splunk Cloud Platform environment may be inaccessible for customers. Please refer to the current live updates from GCP here - https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW Our teams are monitoring the status of the outage. Your patience is greatly appreciated and we will provide more updates upon resolution.

2. 12 giugno 2025 alle ore 19:56 UTCidentified

   We are continuing to work on a fix for this issue.

3. 12 giugno 2025 alle ore 21:59 UTCmonitoring

   A fix has been implemented. We are monitoring to confirm full service recovery. Additional details can be found here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

4. 12 giugno 2025 alle ore 23:01 UTCresolved

   This incident has been resolved.

1. 5 giugno 2025 alle ore 19:14 UTCidentified

   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.

2. 6 giugno 2025 alle ore 21:21 UTCmonitoring

   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.

3. 7 giugno 2025 alle ore 01:22 UTCresolved

   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 .

1. 30 maggio 2025 alle ore 22:52 UTCidentified

   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.

2. 31 maggio 2025 alle ore 06:35 UTCidentified

   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.

3. 3 giugno 2025 alle ore 22:02 UTCresolved

   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.