Splunk OnCall experienced a notice incident on June 24, 2019, lasting 54m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 24, 2019, 12:28 PM UTC
We are currently investigating accessibility issues for some users.
- monitoring Jun 24, 2019, 12:45 PM UTC
We have identified upstream issues that impacted the VictorOps domain. We are continuing to monitor any issues.
- monitoring Jun 24, 2019, 01:05 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 24, 2019, 01:23 PM UTC
This incident has been resolved. VictorOps was affected by an upstream route leak impacting CloudFlare IPs. Please refer to the CloudFlare StatusPage for further detail: https://www.cloudflarestatus.com/. Apologies for any challenges and inconveniences. VictorOps has returned to full functionality.
- postmortem Jun 27, 2019, 03:26 PM UTC
On Monday, from 6:01am to 6:30am MDT \(UTC -6\) VictorOps was affected by the upstream connectivity challenges that impacted large swaths of the internet. For more details on the incident please visit the [Cloudflare Status page](https://www.cloudflarestatus.com/), and [Cloudflare's explanation of what happened](https://blog.cloudflare.com/how-verizon-and-a-bgp-optimizer-knocked-large-parts-of-the-internet-offline-today/). Please know that at VictorOps we take any service disruption very seriously. We have conducted our own internal post-incident review about this event and have taken measures to refine and improve to our response time to incidents like the one we experienced on Monday. As always, we welcome and encourage you to reach out to the VictorOps Support team with any questions: [[email protected]](mailto:[email protected])