The incident is now resolved. For reference, the service disruption we experienced occurred from 10:20AM - 10:39AM (Mountain) this morning. End-users may have experienced performance challenges with our Web and Mobile clients during this time period as well as alerting. We apologize for any unintended inconvenience.
If you have any immediate questions in relation to this incident, please contact our Support team at:
Again, our apologies for any unintended inconveniences this issue may have caused.
Posted Feb 26, 2019 - 18:05 UTC
Update
We are continuing to monitor for any further issues.
Posted Feb 26, 2019 - 18:02 UTC
Update
A fix has been implemented and we are monitoring the results.
Posted Feb 26, 2019 - 17:44 UTC
Update
We are continuing to monitor for any further issues.
Posted Feb 26, 2019 - 17:44 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Feb 26, 2019 - 17:43 UTC
Update
We are continuing to investigate this issue.
Posted Feb 26, 2019 - 17:41 UTC
Update
We are continuing to investigate this issue.
Posted Feb 26, 2019 - 17:36 UTC
Investigating
Please be advised that we are investigating a service disruption associated to our Web and Mobile clients. We are actively investigating the issue. If you have any immediate questions, please contact our Support team at victorops-support@splunk.com
We will be providing Status Page updates as they arrive.
Posted Feb 26, 2019 - 17:32 UTC
This incident affected: Delivery Systems (Notifications - SMS, Notifications - Google Push, Notifications - Apple Push, Notifications - Phone), Splunk On-Call Alert Processing & Integrations (Alert Ingestion, Alert Ingestion - Inbound email, API, Webhooks, Chat integration - Slack, Control Call - Audio Conferencing, Okta SCIM - Provisioning / De-provisioning), Clients (Web Client (Portal), Android Client - Mobile App, iOS Client - Mobile App), and Website (Reporting, Chat integration - Omni-Channel (In-product Chat)).