Splunk On-Call Reporting - On-Call Review Report data is degraded

Incident Report for Splunk On-Call

Monitoring

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
Posted Oct 17, 2025 - 14:46 MDT

Update

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.
Posted Oct 14, 2025 - 17:35 MDT

Update

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.
Posted Oct 13, 2025 - 16:53 MDT

Update

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.
Posted Oct 10, 2025 - 16:12 MDT

Update

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.
Posted Oct 09, 2025 - 15:23 MDT

Update

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.
Posted Oct 08, 2025 - 16:23 MDT

Update

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.
Posted Oct 07, 2025 - 15:22 MDT

Update

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.
Posted Oct 06, 2025 - 18:25 MDT

Update

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.
Posted Oct 03, 2025 - 22:16 MDT

Identified

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.
Posted Oct 03, 2025 - 09:11 MDT
This incident affects: Website (Reporting).