Historical record of incidents for BrainStorm
Report: "Unable to log into the BrainStorm platform"
Last updateThis incident has been resolved.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "BrainStorm Help Center currently down"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Dashboard data is not up-to-date"
Last updateWe believe an outage with a third party resource caused connectivity issues with the data that we use to keep our dashboards up to date. After the outage was resolved, we re-established connection by restarting the infrastructure resources that stream the data.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Report: "Start Flow Button"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue. What is happening: Admins cannot start a Flow manually for a user or group using the "Start Flow" button even if it does have a communication asset.
We are currently investigating this issue.
Report: "Some links reporting "Privacy Error""
Last updateThis incident has been resolved. A problem was found with a third-party cloud resource with the SSL certificate binding causing intermittent use of an incorrect certificate. The resource was re-deployed which resolved the issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Some links in Emails or Teams app are giving a Privacy Error in the browser when clicked on, indicating that they are not formed using HTTPS. We are currently investigating this issue.
Report: "Reporting/Dashboards"
Last updateThis incident has been resolved.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Authentication issue"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue mainly affects the look of the login page but does not affect actual authentication.
The issue has been identified and a fix is being implemented.
We are continuing to investigate this issue.
We are currently investigating this issue. If you are already logged in, this will not affect you.
Report: "Admin Portal - flow engagement performance report errors"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are investigating an issue on the flow engagement performance reporting. If an admin clicks on an element of the sankey diagram they will receive an error message rather than detailed engagement information.
Report: "Flow playback"
Last updateWhen trying to start a Flow the user will get "Flow Not Found" message.
Report: "Unable to register for Events"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Report: "Admin Portal asset assignments degraded."
Last updateHigh traffic created by expired licenses. Content assignments and licensing may be degraded.
Report: "Asset assignments may be degraded."
Last updateSome low-priority asset assignment queues are high and may be slow to resolve due to traffic on the system.
Report: "Admin portal degraded"
Last updateUnable to edit/publish flows.
Report: "Authentication/Login DOWN"
Last updateUsers are unable to log into the BrainStorm Admin and End-user Portals.
Report: "This is an example incident"
Last updateWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
Empathize with those affected and let them know everything is operating as normal.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.