Splunk OnCall experienced a minor incident on February 28, 2024 affecting Reporting, lasting 14h 48m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 28, 2024, 08:57 AM UTC
We are currently experiencing lag in our report tooling. New Incidents will not show-up in any reports until the incident is resolved.
- identified Feb 28, 2024, 08:58 AM UTC
We have identified the issue and are working towards a resolution.
- identified Feb 28, 2024, 04:28 PM UTC
Apologies for the Reporting inconvenience! Current Status: - Data is up to date as of 6:00 AM (UTC) - No reporting data lost - Data replication is in progress and will be 100% available once complete Please direct any questions to Splunk On-Call Support: https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/
- monitoring Feb 28, 2024, 07:24 PM UTC
UPDATE: Remediation complete; watching the latency decrease. Thanks again for your patience while we work this issue to resolution.
- monitoring Feb 28, 2024, 09:08 PM UTC
UPDATE: Reporting back to Operational status. We continue to monitor our Reporting data and will be keeping this incident open for the time being. Thanks again for your patience while we work to completely resolve this incident.
- resolved Feb 28, 2024, 11:46 PM UTC
This incident has been resolved. Reporting is fully operational. We apologize again for any inconvenience. Please direct any questions regarding this incident to On-Call Support: https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/