Splunk OnCall Outage History

Started Oct 15, 2026, 07:46 AM UTC· resolved Oct 15, 2026, 10:36 AM UTC

1. investigating Oct 15, 2026, 07:46 AM UTC

   We are currently investigating this issue.

2. monitoring Oct 15, 2026, 09:30 AM UTC

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

3. resolved Oct 15, 2026, 10:36 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 07:53 PM UTC· resolved Sep 18, 2026, 12:43 AM UTC

1. investigating Sep 14, 2026, 07:53 PM UTC

   We are currently investigating a loading issue affecting the portal.victorops.com web interface. We will provide further details as soon as they are available. We apologize for any inconvenience! Please reach out to the Splunk On-Call Support team with any questions: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

2. investigating Sep 14, 2026, 07:53 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 14, 2026, 11:00 PM UTC

   The issue has subsided. We are continuing to monitor results. Please contact our support team if you still notice any problems or have any questions: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

4. resolved Sep 18, 2026, 12:43 AM UTC

   This incident has been Resolved.

Read the full incident report →

Started Aug 12, 2026, 06:30 AM UTC· resolved Aug 12, 2026, 06:30 AM UTC

1. resolved Aug 13, 2026, 10:30 PM UTC

   Splunk On-Call experienced loading issues affecting the portal.victorops.com web interface and the Android and iOS mobile applications. The disruption lasted approximately one hour and has been resolved. We apologize for any inconvenience this disruption may have caused.

Read the full incident report →

Started Mar 23, 2026, 05:10 PM UTC· resolved Mar 24, 2026, 05:14 PM UTC

1. identified Mar 23, 2026, 05:10 PM UTC

   Spunk On-Call Custom Paging Policies: We've identified an issue that inadvertently impacts Custom Paging Polices. Our Engineering team is working on a fix as soon as possible. In the meantime, please revert to a diversified Primary Paging policy in your User profile so as not to miss critical notification. Helpful Paging Policy documentation: --------------- Splunk On-Call Custom Paging Policies: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/notifications/primary-paging-policy#configure-a-custom-paging-policy-0 Splunk On-Call Primary Paging Policies: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/notifications/primary-paging-policy#configure-a-primary-paging-policy-0 --------------- We apologize for the inconvenience! Please reach out to the Splunk On-Call Support team with any questions: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

2. identified Mar 23, 2026, 10:39 PM UTC

   We continue to work towards a fix for this issue. Please ensure your Primary Paging Policy is sufficient for receiving critical alerts until this issue is resolved. Helpful Paging Policy documentation: --------------- Splunk On-Call Custom Paging Policies: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/notifications/primary-paging-policy#configure-a-custom-paging-policy-0 Splunk On-Call Primary Paging Policies: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/notifications/primary-paging-policy#configure-a-primary-paging-policy-0 --------------- Thanks for your continued patience while we work this issue to resolution. We apologize for the inconvenience! Please reach out to the Splunk On-Call Support team with any questions: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

3. resolved Mar 24, 2026, 05:14 PM UTC

   The Splunk On-Call Custom Paging Policy feature is back to a fully operational status. This incident has been resolved. Thank you for your patience while we resolved this issue. We apologize for any inconvenience! Please reach out to the Splunk On-Call Support team with any questions: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started Dec 05, 2025, 08:47 AM UTC· resolved Dec 05, 2025, 09:12 AM UTC

1. resolved Dec 05, 2025, 09:52 PM UTC

   Splunk On-Call experienced an isolated network disruption between approximately 08:47 UTC - 09:12 UTC earlier today, December 5th. The functionality has since returned to operational. We apologize for any disruption or adverse impact this caused. Please contact Splunk On-Call support with any questions - https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started Nov 13, 2025, 03:35 PM UTC· resolved Nov 13, 2025, 04:54 PM UTC

1. investigating Nov 13, 2025, 03:35 PM UTC

   Splunk On-Call Email Alert Ingestion appears to be disrupted. Thanks for your patience while we investigate this issue. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

2. monitoring Nov 13, 2025, 04:00 PM UTC

   We are now seeing successful delivery of email alerts in our system. We are moving status to monitoring while we investigate the cause for this disruption. Thanks for your patience while we continue to investigate. Updates to follow. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

3. resolved Nov 13, 2025, 04:54 PM UTC

   We've identified this issue as stemming from a release by our Email Alert provider. Their release has been rolled back and now Email Alert delivery to On-Call is fully operational. Our apologies for this disruption. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started Oct 20, 2025, 08:40 AM UTC· resolved Oct 21, 2025, 02:30 AM UTC

1. investigating Oct 20, 2025, 08:40 AM UTC

   Please bear with us while we troubleshoot this issue — updates to follow. Where possible, please adjust your personal paging policies to Push notification and email. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

2. identified Oct 20, 2025, 09:47 AM UTC

   The issue has been identified and is related to an ongoing AWS incident affecting multiple services: https://health.aws.amazon.com/health/status Please continue to diversify your paging policies to incorporate Push and email. ------------- Current AWS status: Increased Error Rates and Latencies Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information. Oct 20 2:22 AM PDT We have applied initial mitigations and we are observing early signs of recovery for some impacted AWS Services. During this time, requests may continue to fail as we work toward full resolution. We recommend customers retry failed requests. While requests begin succeeding, there may be additional latency and some services will have a backlog of work to work through, which may take additional time to fully process. We will continue to provide updates as we have more information to share, or by 3:15 AM.

3. identified Oct 20, 2025, 10:42 AM UTC

   Our cloud telephony partner (SMS and Voice) is seeing partial recovery and is scaling their systems to handle the influx of traffic and processing of notifications. ----- AWS update: Increased Error Rates and Latencies Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled as they work toward full resolution.

4. monitoring Oct 20, 2025, 11:01 AM UTC

   AWS fix has been implemented. We are seeing the successful delivery of SMS and Voice through our notification provider. However, there still may be a backlog of notifications to be processed. Moving incident status to Monitoring. Where possible, to avoid single points of failure, please take action to diversify your On-Call personal paging policies to include all forms of notification: SMS, Voice, Push, WhatsApp Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

5. monitoring Oct 20, 2025, 04:02 PM UTC

   We are continuing to montior the situation. Currently SMS notifications are delivering as normal. However, Voice/Call notification are deeply backlogged and you may experience repeated calls for incidents that have already been actioned in your On-Call instance. We are working directly with our notification provider to help migitate this isse as soon as possible. Where possible, to avoid single points of failure, please take action to diversify your On-Call personal paging policies to include all forms of notification: SMS, Voice, Push, WhatsApp Thank you for your contnued patience while we work to resolve this issue. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

6. monitoring Oct 20, 2025, 08:17 PM UTC

   Call/Voice queues have now cleared and we are seeing voice notifications being delivered in real time again. Currently, all notification types are operational and working as expected. We are continuing to monitor notification rates and will provide further updates on this Status Page Incident as the ongoing AWS incident progresses. Thank you for your continued patience while we work to resolve this issue. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

7. monitoring Oct 20, 2025, 09:57 PM UTC

   We are continuing to monitor for any further issues.

8. resolved Oct 21, 2025, 02:30 AM UTC

   We are no longer experiencing any issues involving delayed or failed SMS or Phone call notification delivery. Please contact Splunk On-Call support if you encounter any further problems. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started Oct 03, 2025, 03:11 PM UTC· resolved Jan 09, 2026, 09:30 PM UTC

1. identified Oct 03, 2025, 03:11 PM UTC

   We are currently experiencing inaccurate reporting data in the On-Call Review report (OCR) within the web client. This is a known issue, and we're working on a fix as soon as possible. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Our apologies for this issue! Please stay tuned to this status page for updates! Thank you for your patience while we work towards a resolution.

2. identified Oct 04, 2025, 04:16 AM UTC

   Update: Please bear with us as we continue to work on a fix for this issue. If you are affected and require immediate On-Call Review reporting data, please reach out to Support via a support ticket or through in-product live chat. We'll gladly provide an accurate, manually generated CSV of the data you are searching for in the On-Call Review report upon request. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Again, our apologies for this issue! Please stay tuned to this status page for further updates! Thank you for your patience while we work towards a resolution.

3. identified Oct 07, 2025, 12:25 AM UTC

   We continue to work on a fix for this issue. If you are affected and require immediate attention, please reach out to Support via a support ticket or through in-product live chat. We've upgraded this incident to Major, as we are currently unable to provide an accurate CSV for the On-Call Review at this time. We've prioritized this issue with our Engineering teams. They are addressing the issue with urgency. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Our apologies again for this issue! Please stay tuned to this status page for updates! Thank you for your patience.

4. identified Oct 07, 2025, 09:22 PM UTC

   Update: We continue to work on a fix for the On-Call Review reporting feature. The Splunk On-Call Engineering team and senior Support leadership continue to work towards providing you with accurate On-Call Review reporting. Please note that this is a complex problem involving data from many sources. Our teams are working urgently and diligently, with accurate On-Call-Review data as our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

5. identified Oct 08, 2025, 10:23 PM UTC

   Update: Please bear with us as we continue to work on a fix for the On-Call Review reporting feature. The Splunk On-Call Engineering team and Senior Support leadership continue to work towards providing you with accurate On-Call Review reporting. ** Please note that this is a complex problem involving data from different sources. Our teams are working urgently and diligently, with accurate On-Call-Review data as our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

6. identified Oct 09, 2025, 09:23 PM UTC

   Update: Please bear with us as we continue to work on a fix for the On-Call Review reporting feature. The Splunk On-Call Engineering team and Senior Support leadership continue to work towards providing you with accurate On-Call Review reporting. ** Please note that this is a complex problem involving data from different sources. Our teams are working urgently and diligently, with accurate On-Call-Review data as our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

7. identified Oct 10, 2025, 10:12 PM UTC

   Update: Our Engineering and Support teams continue to give our full attention to resolving this issue as soon as possible. ** Please note that this is a complex problem involving data from different sources. Our teams are working urgently and diligently, with accurate On-Call-Review data as our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

8. identified Oct 13, 2025, 10:53 PM UTC

   Splunk On-Call Engineering and Support teams continue to give our full attention to resolving this issue as soon as possible. ** Please note that this is a complex problem. Our teams are working urgently and diligently towards providing our customers with accurate On-Call-Review data. It is our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

9. identified Oct 14, 2025, 11:35 PM UTC

   Splunk On-Call Engineering and Support teams continue to give our full attention to resolving this issue as soon as possible. ** Please note that this is a complex problem. Our teams are working urgently and diligently towards providing our customers with accurate On-Call-Review data. It is our top priority. If you are affected by this reporting feature, please reach out to On-Call Support. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Thank you again for your patience while we work to resolve this incident and the accuracy of the On-Call Review report.

10. monitoring Oct 17, 2025, 08:46 PM UTC

    We want to update you on the status of the On-Call Review report issue. Our team has implemented several fixes to address the root cause, and as a result, we are reducing the incident severity to "Minor" and updating the status to "Monitoring" while we complete final data validation. We recognize that some issues with how On-Call Reporting data appears in the UI are still present. Please know that our engineering team is working diligently to fully resolve these remaining problems. If this issue is impacting your access to On-Call Review reporting data and you need information urgently, please contact our Support team by submitting a ticket or using the in-product live chat. Upon request, we’re happy to provide a manually generated CSV containing the accurate data you need from the On-Call Review report. Thank you for your understanding and patience as we work to fully resolve this incident. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

11. monitoring Oct 31, 2025, 10:21 PM UTC

    Issues with On-Call Reporting data still appear in the UI. Please know that our engineering team continues to work on these remaining problems. If this issue is impacting your access to On-Call Review reporting data and you need information, please contact our Support team by submitting a ticket or using the in-product live chat. Upon request, we’re happy to provide a manually generated CSV containing the accurate data you need from the On-Call Review report. Thank you for your understanding and patience as we continue our work to fully resolve this incident. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

12. resolved Jan 09, 2026, 09:30 PM UTC

    Issue Summary: An issue was introduced during an early-notification feature rollout, which prevented certain on-call and off-call entries from being saved to our primary database. This resulted in inaccurate reporting, with on-call hours appearing either higher or lower than actual values for affected users. Contact Us: https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support Again, our apologies for this issue! Thank you for being so patient while we worked towards a resolution.

Read the full incident report →

Started Aug 13, 2025, 09:47 PM UTC· resolved Aug 13, 2025, 11:00 PM UTC

1. investigating Aug 13, 2025, 09:47 PM UTC

   Please bear with us while we troubleshoot this issue; updates will follow. Note, this issue DOES NOT affect the functionality of previously downloaded iOS apps. Android is unaffected. For questions or concerns regarding the iOS Mobile App availability, please reach out to Splunk On-Call Support: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/contact-splunk-on-call-support

2. resolved Aug 13, 2025, 11:00 PM UTC

   This incident has been resolved. The iOS Mobile App for On-Call is once again available in the Apple App Store. Apologies for any inconvenience! Please send any questions regarding this issue to Splunk On-Call Support: https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started Jun 04, 2025, 07:55 AM UTC· resolved Jun 04, 2025, 09:45 AM UTC

1. investigating Jun 04, 2025, 07:55 AM UTC

   The Splunk On-Call portal is currently unavailable via web and mobile. We are actively working to resolve this issue as quickly as possible. If you have any immediate questions or concerns, our support team is standing by to respond: 1 (855) 775-8657 https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/

2. identified Jun 04, 2025, 08:27 AM UTC

   We've identified this issue related to a deploy inadvertently impacting our databases and are working to stabilize. The Web Client is coming back on line now. Thank you for your patience while we coming back on line.

3. monitoring Jun 04, 2025, 08:36 AM UTC

   Update: A fix has been implemented and we are monitoring the issue. The On-Call timeline is still experiencing loading issues. We are seeing high alert-lag across the platform.

4. monitoring Jun 04, 2025, 08:56 AM UTC

   We continue to monitor the situation. We are still experiencing high alert lag. The Web Client and Mobile Apps are now accessible. Thanks for your patience while we continue to work this issue to resolution.

5. resolved Jun 04, 2025, 09:45 AM UTC

   This incident is now resolved. The Splunk On-Call web client and mobile applications are fully operational. We apologize for the inconvenience. Please reach out to the Splunk On-Call support team with any questions. https://help.splunk.com/en/splunk-observability-cloud/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support

Read the full incident report →

Started May 14, 2025, 05:25 PM UTC· resolved May 14, 2025, 10:25 PM UTC

1. investigating May 14, 2025, 05:25 PM UTC

   Emails sent to the Generic Email Endpoint Integration are not being ingested by On-Call. These emails are not creating incidents or other alerts as expected. All other Integrations and On-Call incident operations are fully operational at this time. We are currently investigating this issue. Please monitor this Statuspage for the most up to date information, we will post another update shortly

2. identified May 14, 2025, 05:59 PM UTC

   We have identified the source of this issue and are actively working to deploy a fix.

3. monitoring May 14, 2025, 09:25 PM UTC

   A fix has been implemented and we are monitoring the results. Stand by for confirmation

4. resolved May 14, 2025, 10:25 PM UTC

   This incident is now resolved. Alert Ingestion - Inbound email is now fully operational. We apologize for this inconvenience. If you continue to experience issues with your inbound email alerts, please reach out to On-Call Support as soon as possible! https://docs.splunk.com/observability/en/sp-oncall/admin/get-started/spoc-support.html

Read the full incident report →

Started Oct 26, 2024, 09:45 AM UTC· resolved Oct 26, 2024, 11:03 AM UTC

1. investigating Oct 26, 2024, 09:45 AM UTC

   Please bear with us while we investigate this issue—impacted components Single Sign On (SSO) Updates to follow. We apologize for this inconvenience. Please reach out to On-Call Support with any questions. https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/

2. identified Oct 26, 2024, 10:23 AM UTC

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

3. monitoring Oct 26, 2024, 10:52 AM UTC

   A fix has been implemented and we are monitoring the solution. SSO is back to an operational state.

4. resolved Oct 26, 2024, 11:03 AM UTC

   This incident has been resolved. Single Sign On (SSO) is fully operational. We apologize for this inconvenience. If you continue to experience issues with your SSO connections, please reach out to On-Call Support as soon as possible! https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/

Read the full incident report →