Sisense incident
Sisense for Cloud Data Teams Database Connection Errors
Sisense experienced a notice incident on June 24, 2021 affecting Sisense for Cloud Data Teams, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- monitoring Jun 24, 2021, 06:44 PM UTC
Starting at 10:22am PST, some Sisense for Cloud Data Teams customers database connections experienced connection errors due to a recent code change. Engineers rolled back the code at 10:53am PST and are monitoring the connections. The Sisense Cloud Support Team can be reached at [email protected] or via live chat.
- monitoring Jun 24, 2021, 07:28 PM UTC
Some Sisense for Cloud Data Teams customers database connections are still experiencing errors from the previous changes. Engineers are working to re-start those connections and will be monitoring. The Sisense Cloud Support Team can be reached at [email protected] or via live chat.
- monitoring Jun 24, 2021, 08:03 PM UTC
Sisense for Cloud Data Teams engineers have restarted the connection services and databases are connecting as normal. The Engineers are monitoring for any further issues. The support team can be reached at [email protected] or via live chat for further questions.
- resolved Jun 24, 2021, 08:32 PM UTC
Sisense for Cloud Data Teams engineers have resolved the underlying cause of the ST003 connection errors. Some users may still have lingering errors. For these users, a database admin will have to unblock the Sisense user before full functionality can be restored. Please have a database admin execute mysqladmin flush-hosts For further details, please refer to: https://dev.mysql.com/doc/refman/5.6/en/host-cache.html#host-cache-flushing