Is there an Sisense outage?
Sisense status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Sisense and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Sisense and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Sisense.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Sisense for Cloud Data Teams | Active |
| Sisense Managed Service | Active |
View the latest incidents for Sisense and check for official updates:
Description: Intercom has identified the cause of the issue and provided a fix. Live chat is now available.
Status: Resolved
Impact: None | Started At: Sept. 1, 2020, 4:05 p.m.
Description: Cloudflare's status page has been moved to resolved. Sisense is accessible to all users and all caching updates are now operational. The Sisense Cloud Support Team can be reached at [email protected].
Status: Resolved
Impact: Critical | Started At: July 17, 2020, 9:23 p.m.
Description: The Sisense application is now connecting to databases as expected. The Sisense Cloud Support Team can be reached at [email protected].
Status: Resolved
Impact: Major | Started At: May 30, 2020, 8:03 p.m.
Description: The following is the incident report for the Sisense incident that occurred on May 28, 2020 from 11:35 AM PST to 11:50 AM PST. This issue specifically affected all customers using the Sisense for Cloud Data Teams web application. These customers were not able to access Sisense for Cloud Data Teams as well as some background work may have been interrupted, delayed or lost during the outage period . We understand the impact this had on our customers and sincerely apologize. We have taken a number of steps to prevent this issue from occurring in the future as detailed further below. **ISSUE SUMMARY** Our investigation into the issue found that the outage occurred when the underlying hardware for one of our databases supporting Sisense for Cloud Data Teams crashed and did not failover for 15 minutes due to an underlying issue with AWS. This caused the web application to go down during this period. As part of our efforts to rectify the system, the database was restarted and all services were restored. This brought the web application back up and all customers were able to access Sisense for Cloud Data Teams. **REMEDIATION** We are confident that we have identified the necessary corrections and are equipped to handle similar outages in the future. The team is committed to creating the most reliable data platform possible. As a response to this issue, we've made key improvements to our infrastructure: * Editing our error reporting verbiage to ensure that internal errors were clearly described * Working with our cloud provider to understand and reduce time of impact for hardware failures. * Adding better error pages so customers can know how to access support and the status page For more information, please reach out to our Solutions Team at [[email protected]](mailto:[email protected]) or via live chat.
Status: Postmortem
Impact: Critical | Started At: May 28, 2020, 6:45 p.m.
Description: The following is the incident report for the Sisense incident that occurred on May 18, 2020 from 8:44 AM PST to 5:30 PM PST. This issue specifically affected customers on the community cache clusters. These customers were not able to access their usage data for the period of the outage. We understand the impact this had on our customers and sincerely apologize. We have taken a number of steps to prevent this issue from occurring in the future as detailed further below. **ISSUE SUMMARY** Our investigation into the issue found that the system degradation occurred due to the Usage Data Redshift clusters being incorrectly deleted as part of a larger efficiency project. These clusters should have been flagged for non-deletion but earlier modification to the code led to this flag being removed. As part of our efforts to rectify the system, the clusters were restored based off of an earlier snapshot. This restore allowed customers to be able to access and query their usage data again. **REMEDIATION** We are confident that we have identified the necessary corrections and are equipped to handle similar upgrades in the future. The team is committed to creating the most reliable data platform possible. As a response to this issue, we've made key improvements to our infrastructure: * Set up processes and checks to prevent Usage Data clusters from being deleted. * Set up additional critical alerts to detect missing Usage Data clusters For more information, please reach out to our Solutions Team at [[email protected]](mailto:[email protected]) or via live chat.
Status: Postmortem
Impact: Minor | Started At: May 18, 2020, 11:03 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
