Feb 8, 01:15 UTC
Resolved - This incident has now been resolved. The issue was related to a settings update which impacted our database. We will investigate the root cause behind how this happened and implement steps in order to prevent it happening again in the future. We are sorry for any inconvenience that may have been caused to your meetings and events.
Feb 8, 01:05 UTC
Monitoring - A fix has been implemented and we're monitoring for the results.
Feb 7, 23:56 UTC
Identified - We have identified the cause of the issue and have implemented some changes. We will continue monitoring everything closely to ensure Slido returns to normal.
Feb 7, 23:04 UTC
Investigating - We are investigating elevated error rates with Slido which may cause issues with access or performance. Our technical team is actively investigating, and we'll update you here as soon as we have more information.
Should you require immediate assistance, please contact [email protected].
Thank you for your patience.
Sep 19, 06:31 UTC
Resolved - This incident has been resolved.
Sep 16, 23:39 UTC
Update - The root cause of the issue was the mismatch in the root DNS records for one of the domains we use to provide the service. The issue was identified and escalated very quickly; however, our hands were tied, and it took some time until the root registry applied all the necessary fixes.
We are continuing to monitor for any further issues, but we anticipate that some clients might experience certain troubles in the course of the next 48 hours. The reason is that corrupted DNS records might still be present in the browsers and even distributed by some ISPs. Any issues will disappear automatically, but in case you need any assistance with troubleshooting or understanding the situation, please, don't hesitate to reach out to us at [email protected]
We are very sorry for all the trouble and inconvenience.
Sep 16, 23:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 16, 23:16 UTC
Update - We are currently working on restoring all Slido functionality. There are still problems that we have not been able to fully resolve - mainly connected with the login into the accounts, because of this, we are currently unable to provide a reliable ETA for when full functionality will be restored.
Sep 16, 21:08 UTC
Investigating - We have received reports from clients that various components of Slido don't load. We are investigating underlying issues and will give update an update as soon as possible.
Sep 27, 09:42 UTC
Resolved - The incident has been resolved at 8:00 UTC. We apologise for the inconvenience.
Sep 27, 07:21 UTC
Update - Initial investigations have confirmed that is only affecting users logging in through the Webex integration. SSO through other integrations is working as expected
Sep 27, 07:13 UTC
Investigating - We are investigating issues that might be affecting some customers. Logging into Slido through SSO might result in errors.
Our team is on it and trying to identify the root cause. Please bear with us as we continue to investigate.
Jan 18, 08:00 UTC
Resolved - On Wednesday 18th, between 8:54 AM to 11:52 AM CET, some Slido users experienced errors when using the “Present in fullscreen” option in Slido admin.
These errors were a result of the work we are doing to replace our old authorization system with a modern OAuth 2.0-based system. Doing this for a set of interdependent systems during regular operations is a bit like replacing brakes on a car while it’s in motion.
When making a change for our apps to engage the new Auth system along with the old, the use-case of Slido Admin passing on its authorisations to Slido Wall was made to request auth scope that the auth system was not yet prepared to grant, resulting in “not logged in” error message.
We’d like to apologize to our customers who were impacted by this disruption. If you have any other questions, please let us know at [email protected].
Jan 19, 10:00 UTC
Resolved - Between Wednesday 18th and Thursday 19th of January, Slido users may have experienced issues (e.g. not seeing new questions, likes, or poll results arriving) if they didn't reload Slido Admin for more than 10 minutes.
These problems were a result of the work we are doing to replace our old authorization system with a modern OAuth 2.0-based system. This authorization system controls what users are able to do and see within Slido. Doing this for a set of interdependent systems during regular operations is a bit like replacing brakes on a car while it’s in motion.
We are changing from making authorization decisions individually for every single request to a new system, where we make the decision once and embed the information about what the user has access to.
For security reasons, these tokens expire after 10 minutes and need to be exchanged for a new token. In this instance, there was a problem with the renewed token being shared with the technology that enables the continual updates to be seen with Slido admin.
We’d like to apologize to our customers who were impacted by this disruption. If you have any other questions, please let us know at [email protected].
Jan 22, 11:01 UTC
Completed - The scheduled database maintenance has been completed successfully.
Slido services were unavailable for approximately two minutes - between 8:16 - 8:17 UTC and 8:24 - 8:25 UTC.
This tiny interruption will make Slido healthier, more secure and more reliable than before.
Thank you for your understanding and patience. Have a great rest of the day!
Jan 22, 10:43 UTC
Verifying - Verification is currently underway for the maintenance items.
Jan 22, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 5, 13:07 UTC
Scheduled - It's time for a break. We need to perform several database upgrades to make Slido healthier, more secure and more reliable than before.
The maintenance will happen on January 22 (Sunday) between 07:00 UTC - 12:00 UTC.
Slido may be unavailable for 2-3 minutes. We recommend not using Slido for any critical meetings or events during the maintenance window to avoid surprises.
Thanks for your understanding!
Jan 25, 12:30 UTC
Resolved - Between 1.50pm CET & 3.28pm CET on Wednesday 25th January, Slido users may have experienced issues with receiving new participant questions on the present view.
These problems were due to a release which has now been reverted. Slido's present view should now be updating as expected. If you are still experiencing issues, please refresh the page by using Shift+Cmd (Apple) or Ctrl+R (Windows).
We are sorry for any inconvenience this caused to you and your meetings, if you have any feedback or are still facing problems, please contact [email protected].
Mar 26, 07:00 UTC
Completed - The scheduled maintenance has been completed.
Mar 26, 06:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 23, 11:55 UTC
Scheduled - It's time for a quick break. We need to perform a Redis upgrade to make Slido healthier, more secure and more reliable than before.
The maintenance will happen on March 26 (Sunday) between 06:00 UTC - 07:00 UTC.
During this time, updating of voting in polls, submitting a question, upvoting, and reorganizing questions by the popularity in the Q&A might be slower in most Slido apps due to slower WebSockets messages in our platform. However, any websocket issues should only occur occasionally during this period. We recommend not using Slido for any critical meetings or events during the maintenance window to avoid surprises.
This small interruption will make Slido healthier, more secure and more reliable than before.
Thanks for your understanding!
May 23, 16:08 UTC
Resolved - This incident has now been resolved.
May 23, 16:03 UTC
Monitoring - Webex integration is working now, we are still monitoring its status as we work towards fully resolving the issue.
May 23, 14:24 UTC
Investigating - We are investigating issue with Slido Webex integration.
Slido as a standalone product works without issues.
Our team is working with Webex team to identify the root cause. Please bear with us as we continue to investigate.
May 24, 20:47 UTC
Resolved - This incident has now been resolved.
May 24, 20:42 UTC
Monitoring - Webex integration is working now, we are still monitoring its status as we work towards fully resolving the issue.
May 24, 20:13 UTC
Investigating - We are investigating issue with Slido Webex integration.
Slido as a standalone product works without issues.
Our team is working with Webex team to identify the root cause. Please bear with us as we continue to investigate.