IsDown continuously monitor the official VictorOps status page for ongoing outages. Check the stats for the latest 30 days and a list of the last VictorOps outages.
Number of Outages
3
Average Downtime
144 mins
Total Downtime
434 mins
Since last incident
13 days
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including VictorOps, and never miss an outage again.
Minor · 13 days ago · lasted 16 minutes
Apologies for the inconvenience. We are investigating a loading issue on the Incidents Tab affecting the Team Incidents Dashboard. Please refer to the People Pane in the Timeline tab for this information. Updates to follow.
Major · 21 days ago · lasted about 6 hours
We are currently investigating Timeline and Mobile App loading issues. Please bear with us as we investigate this issue. Please stay tuned for updates.
Major · 28 days ago · lasted about 1 hour
Currently experiencing issues with SSO login for all providers. Please bear with us while we work toward a resolution.
Minor · 5 months ago · lasted 3 days
We are currently investigating disconnects and loading issues to the On-Call timeline that may affect the ability to ACK and RESOLVE active incidents. If you are experiencing any issues with incident actions in the Timeline, please reach out to On-Call Support via https://help.victorops.com/knowledge-base/how-to-contact-splunk-on-call-support/ Our Support hotline may be reached here: (1-855) SPLUNK-S or (1-855) 775-8657 Thank you for your patience while we work this issue to ground. Updates to follow.
Minor · 6 months ago · lasted about 19 hours
Apologies for this inconvenience! Currently, our in-product Live Chat feature is experiencing issues. We are investigating. For immediate Support, please use the Splunk Support Portal (https://login.splunk.com/) or the Call Center: https://www.splunk.com/en_us/about-splunk/contact-us.html#customer-support
Minor · 8 months ago · lasted about 3 hours
Please be aware: we elevated error rates and latencies for invokes on API Gateway endpoints in the US-WEST-2 Region. For more information please visit: https://health.aws.amazon.com/health/status Updates to follow.
Minor · 9 months ago · lasted 3 minutes
We are actively researching a geographically isolated issue related to Phone Notification delivery challenges to the +86 (China) country code. We have escalated this issue to our telecommunications providers and will continue to stay actively engaged in all efforts to resolve this situation. Relevant updates will be provided to this Status Page as they arrive. As we continue to research this issue, we recommend that Splunk On-Call end-users located in China diversify their Splunk On-Call Personal Paging Policy to include Email, SMS, and Push notification delivery as alternatives to Phone. Our apologies for any inconvenience this situation may be causing you and your end-users. Updates to follow.
Minor · 10 months ago · lasted 17 days
We are actively researching a geographically isolated issue related to Phone Notification delivery challenges into the +86 (China) country code. We have escalated this issue to our telecommunications providers and will continue to stay actively engaged in all efforts to resolve this situation. Relevant updates will be provided to this Status Page as they arrive. As we continue to research this issue, we recommend that Splunk On-Call end-users located in China diversify their Splunk On-Call Personal Paging Policy to include Email, SMS, and Push notification delivery as alternatives to Phone. Our apologies for any inconvenience this situation may be causing you and your end-users. Updates to follow.
Get notified only when an outage impacts a certain component.
The data and notifications you need, in the tools you already use.
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including VictorOps, and never miss an outage again.
Try it out! How much time you'll save your team, by having the outages information close to them?