Is there an Sisense outage?
Sisense status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Sisense and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 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: Nov. 24, 2020, 2:04 p.m.
Description: The following is the incident report for the Sisense incident that occurred on October 13th, 2020 between 12:40 PM PDT and 8:16 PM PDT. This issue affected all customers using the Sisense for Cloud Data Teams web application to varying degrees. For brief periods of time between 12:40 - 12:48 PM PDT and 4:23 PM - 5:01PM PDT, customers may have lost access to the application. More commonly, customers were not able to run any new queries during the outage period. We understand the effect 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 found that a database used in running customer queries was unable to accept new writes, effectively becoming read-only. Further investigation revealed that the database load was due to high-contention of the database’s access to shared memory. Resetting and failing over the database cleared the contention but it quickly reappeared, due to bloated indices that were consuming excessive shared memory and causing the database contention. Once the database became effectively read-only, customers weren’t able to run new queries because the new query requests couldn’t be written to the database. To restore application availability, the database was restarted, the affected tables were re-indexed and all associated services were restored. This restart & reindex cycle took place three times during the incident, as multiple tables were affected and could not all be resolved in a single pass. Once complete, all customers were able to access Sisense for Cloud Data Teams and run queries, as normal. **REMEDIATION** We are confident that we have identified appropriate corrections and are equipped to handle any similar outages in the future. The team is committed to creating the most reliable data platform possible. As a response to this issue, we’re making key improvements to our infrastructure: * Tuning our autovacuum settings to clear dead rows more frequently * Adding monitoring around index bloat, which will alert on-call engineers before similar situations can occur in the future. If you have any questions, please reach out to our Solutions Team at [[email protected]](mailto:[email protected]) or via live chat.
Status: Postmortem
Impact: Major | Started At: Oct. 14, 2020, 2:25 a.m.
Description: The following is the incident report for the Sisense incident that occurred on October 13th, 2020 between 12:40 PM PDT and 8:16 PM PDT. This issue affected all customers using the Sisense for Cloud Data Teams web application to varying degrees. For brief periods of time between 12:40 - 12:48 PM PDT and 4:23 PM - 5:01PM PDT, customers may have lost access to the application. More commonly, customers were not able to run any new queries during the outage period. We understand the effect 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 found that a database used in running customer queries was unable to accept new writes, effectively becoming read-only. Further investigation revealed that the database load was due to high-contention of the database’s access to shared memory. Resetting and failing over the database cleared the contention but it quickly reappeared, due to bloated indices that were consuming excessive shared memory and causing the database contention. Once the database became effectively read-only, customers weren’t able to run new queries because the new query requests couldn’t be written to the database. To restore application availability, the database was restarted, the affected tables were re-indexed and all associated services were restored. This restart & reindex cycle took place three times during the incident, as multiple tables were affected and could not all be resolved in a single pass. Once complete, all customers were able to access Sisense for Cloud Data Teams and run queries, as normal. **REMEDIATION** We are confident that we have identified appropriate corrections and are equipped to handle any similar outages in the future. The team is committed to creating the most reliable data platform possible. As a response to this issue, we’re making key improvements to our infrastructure: * Tuning our autovacuum settings to clear dead rows more frequently * Adding monitoring around index bloat, which will alert on-call engineers before similar situations can occur in the future. If you have any questions, please reach out to our Solutions Team at [[email protected]](mailto:[email protected]) or via live chat.
Status: Postmortem
Impact: Critical | Started At: Oct. 13, 2020, 10:17 p.m.
Description: The following is the incident report for the Sisense incident that occurred on October 13th, 2020 between 12:40 PM PDT and 8:16 PM PDT. This issue affected all customers using the Sisense for Cloud Data Teams web application to varying degrees. For brief periods of time between 12:40 - 12:48 PM PDT and 4:23 PM - 5:01PM PDT, customers may have lost access to the application. More commonly, customers were not able to run any new queries during the outage period. We understand the effect 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 found that a database used in running customer queries was unable to accept new writes, effectively becoming read-only. Further investigation revealed that the database load was due to high-contention of the database’s access to shared memory. Resetting and failing over the database cleared the contention but it quickly reappeared, due to bloated indices that were consuming excessive shared memory and causing the database contention. Once the database became effectively read-only, customers weren’t able to run new queries because the new query requests couldn’t be written to the database. To restore application availability, the database was restarted, the affected tables were re-indexed and all associated services were restored. This restart & reindex cycle took place three times during the incident, as multiple tables were affected and could not all be resolved in a single pass. Once complete, all customers were able to access Sisense for Cloud Data Teams and run queries, as normal. **REMEDIATION** We are confident that we have identified appropriate corrections and are equipped to handle any similar outages in the future. The team is committed to creating the most reliable data platform possible. As a response to this issue, we’re making key improvements to our infrastructure: * Tuning our autovacuum settings to clear dead rows more frequently * Adding monitoring around index bloat, which will alert on-call engineers before similar situations can occur in the future. If you have any questions, please reach out to our Solutions Team at [[email protected]](mailto:[email protected]) or via live chat.
Status: Postmortem
Impact: Critical | Started At: Oct. 13, 2020, 7:48 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Oct. 6, 2020, 4:34 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.
