All Systems Operational
Notifications - SMS ? Operational
Notifications - Google Push ? Operational
Notifications - Apple Push Operational
Notifications - Email ? Operational
Notifications - Phone ? Operational
Alert Ingestion ? Operational
Alert Ingestion - Inbound email Operational
API Operational
Web client (portal) ? Operational
Android client ? Operational
iOS client Operational
Chat integration - HipChat ? Operational
Chat integration - Slack ? Operational
Knowledge Base ? Operational
Main website ? Operational
StatusPage Integration Operational
Reporting Operational
SSO Login Operational
Control Call - Audio Conferencing Operational
Billing ? Operational
Webhooks ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 19, 2019

No incidents reported today.

Feb 18, 2019

No incidents reported.

Feb 17, 2019

No incidents reported.

Feb 16, 2019

No incidents reported.

Feb 15, 2019

No incidents reported.

Feb 14, 2019

No incidents reported.

Feb 13, 2019
Resolved - All components have returned to operational, though we are still monitoring activity closely.
Feb 13, 10:41 MST
Update - We identified a disruption in the service related to a deployment at approximately 10:22 am MT. We are now closely monitoring the issue. Please contact victorops-support@splunk.com for any questions or concerns.
Feb 13, 10:35 MST
Update - We are continuing to monitor for any further issues.
Feb 13, 10:31 MST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 13, 10:31 MST
Identified - The issue has been identified and a fix is being implemented.
Feb 13, 10:31 MST
Update - We are continuing to investigate this issue.
Feb 13, 10:28 MST
Investigating - Isolated organizations are experiencing service disruption in the main portal.
Feb 13, 10:27 MST
Feb 12, 2019

No incidents reported.

Feb 11, 2019

No incidents reported.

Feb 10, 2019

No incidents reported.

Feb 9, 2019

No incidents reported.

Feb 8, 2019
Resolved - Production monitoring of the new short code number (see below) has proven successful. Accordingly, we are moving this incident to resolved. Please see below for additional details:

. . .

In response to the isolated SMS notification challenges we were encountering on the AT&T Network, we have provisioned a new short code number. This new short code number should allow for SMS notifications to reach those AT&T end-users that were previously encountering notification challenges.

For reference, the new short code number is: 842867

If you are continuing to encounter SMS notification challenges, please reach out to VictorOps Support team at:

victorops-support@splunk.com

Once again, we apologize for any inconvenience this issue may have caused.
Feb 8, 15:45 MST
Monitoring - In response to the isolated SMS notification challenges we were encountering on the AT&T Network, we have provisioned a new short code number. This new short code number should allow for SMS notifications to reach those AT&T end-users that were previously encountering notification challenges.

For reference, the new short code number is: 842867

If you are continuing to encounter SMS notification challenges, please reach out to VictorOps Support team at:

victorops-support@splunk.com

We apologize for any inconvenience this issue may have caused.
Feb 8, 14:34 MST
Investigating - We are currently investigating isolated reports of end-users on the AT&T network that are failing to receive SMS notifications via the VictorOps platform. Please know that we are actively working on resolving this issue.

Please contact the VictorOps Support team with any immediate questions:

victorops-support@splunk.com

We apologize for any unintended inconvenience. Updates to follow.
Feb 8, 11:42 MST
Feb 7, 2019

No incidents reported.

Feb 6, 2019

No incidents reported.

Feb 5, 2019

No incidents reported.