Slido Outage History

11 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Slido Incident

Slido incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jun 10, 2026Login Issues for Webex Users on all clusters except EU cluster.We have confirmed that the login issues affecting Webex users outside the EU have been resolved. The latest fix has restored normal login access, and our monitoring shows the service is operating normally. We…8h 26mResolved
Jun 10, 2026Login issuesOur team managed to resolve the issue. We will investigate this incident and ensure we take the necessary steps to prevent this from happening again. This is not the experience we are committed to delivering to you and…24 minResolved
Jun 3, 2026Login issuesThis incident has been resolved.1h 18mResolved
Mar 2, 2026Major Outage of United Arab Emirates regionWe now consider this issue to be resolved as we have a functional workaround for users based in the UAE. If you were previously on the UAE server and need access to Slido, please contact support@slido.com and we will be…268h 50mResolved
Mar 2, 2026Major OutageThe issue has now been resolved and the service is operating normally again. Thank you for your patience while this was being addressed.30 minResolved
Feb 10, 2026Degraded performanceThe issue has now been resolved and the service is operating normally again. The problem was caused by an AWS-related outage. We’ve confirmed that DNS lookups are functioning as expected and are continuing to monitor…59 minResolved
Feb 8, 2026Scheduled invoice service maintenanceThe scheduled maintenance has been completed.10h 0mScheduled
Jan 26, 2026Issue with Google Slides Chrome ExtensionOur Google Slides integration should gradually be returning to normal, although it can take a number of days for the new version of the chrome extension to reach you. This is something that we don't have any control…64h 19mResolved
Nov 30, 2025Database maintenanceThe scheduled maintenance has been completed.30 minScheduled
Nov 26, 2025Issue with quiz timerOur team managed to resolve the issue. We will investigate this incident and ensure we take the necessary steps to prevent this from happening again. This is not the experience we are committed to delivering to you and…18 minResolved
Nov 18, 2025Invoice ServicesA fix on a Braintree side has been implemented and incident is now resolved. Our team confirmed payments are working correctly. We apologize for the inconvenience.40 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Slido incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Slido Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Slido acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Slido outage in this window ran 11d 4h, against a mean recovery of 1d 8h. If you depend on Slido in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.