Slido status history
Current state: operational — “All Systems Operational” per https://status.slido.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Slido incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Major Outage of United Arab Emirates region — 11.2 days (2026-03-02 09:36 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-10 02:01 UTC | Login Issues for Webex Users on all clusters except EU cluster. | resolved | critical | 8 h 26 min |
| 2026-06-10 01:00 UTC | Login issues | resolved | major | 24 min |
| 2026-06-03 13:51 UTC | Login issues | resolved | major | 1 h 18 min |
| 2026-03-02 09:36 UTC | Major Outage of United Arab Emirates region | resolved | critical | 11 d 4 h |
| 2026-03-02 09:00 UTC | Major Outage | resolved | critical | 30 min |
| 2026-02-10 21:14 UTC | Degraded performance | resolved | major | 59 min |
| 2026-01-26 23:03 UTC | Issue with Google Slides Chrome Extension | resolved | minor | 2 d 16 h |
| 2025-11-26 18:05 UTC | Issue with quiz timer | resolved | major | 18 min |
| 2025-11-18 12:18 UTC | Invoice Services | resolved | none | 40 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Slido with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"slido"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}