Kahoot Outage History

11 incidents recorded over the last 365 days, 6 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 Kahoot Incident

Kahoot incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 23, 2026[Actimo] Planned network maintenanceThe scheduled maintenance has been completed.54h 0mScheduled
Sep 22, 2026YouTube Video Service DisruptionsThis incident has been resolved.6h 10mResolved
Sep 7, 2026[Actimo] Load balancer maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Aug 9, 2026[Actimo] Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Jun 23, 2026Moderation serviceThe issue with moderation is resolved. All services are fully operational.11h 12mResolved
Apr 7, 2026Game reportsThe issue with accessing reports is resolved. All services are fully operational. Reports are being uploaded and will be made available to customers shortly21 minResolved
Feb 17, 2026[ Motimate ] Scheduled maintenance: Tuesday, 17 February 22:00–04:00 CETThe scheduled maintenance has been completed.6h 0mScheduled
Dec 16, 2025[Actimo] Infrastructure UpgradeThe scheduled maintenance has been completed.1h 30mScheduled
Dec 16, 2025[Actimo] 503s Service UnavailableWe experienced issues connecting from one of our services to our Cloudfront distribution which impacted app usage from 7h24 until 8h05 today. Issue has been resolved0 minResolved
Nov 18, 2025[Motimate] Major Service Outage: Upstream Provider IssuesThis incident has been resolved.3h 41mResolved
Nov 6, 2025[Motimate] Problems accessing InsightsThis incident has been resolved.5h 48mResolved

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 Kahoot 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 Kahoot 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 Kahoot 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 Kahoot outage in this window ran 2d 6h, against a mean recovery of 8h 15m. If you depend on Kahoot 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.