UserZoom Outage History
9 incidents recorded over the last 365 days, 8 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 UserZoom Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 21, 2026 | Scheduled downtime: November 21st 2026On Saturday, November 21, we will be performing an infrastructure upgrade on UserZoom. The platform will be unavailable for up to 12 hours, from 7:00 a.m. to 7:00 p.m. UTC. More information… | 12h 0m | Scheduled |
| Jul 15, 2026 | We're investigating reports that Android 17 users are unable to start UserZoom testsThis incident has been resolved. | 18h 40m | Resolved |
| Apr 22, 2026 | Userzoom downThis incident has been resolved. | 44 min | Resolved |
| Feb 2, 2026 | Studies with Video Questions are causing upload errorsThis incident has been resolved. | 16h 27m | Resolved |
| Jan 15, 2026 | Downloading/Sharing Clips currently not working for users in the USThis incident has been resolved. | 16h 37m | Resolved |
| Jan 14, 2026 | Unable to log into UserZoomThis incident has been resolved. | 51 min | Resolved |
| Dec 10, 2025 | Unable to log into UserZoomThis incident has been resolved. | 45 min | Resolved |
| Dec 1, 2025 | Connectivity issues in EuropeThis incident has been resolved. | 38 min | Resolved |
| Nov 5, 2025 | Data exports failing for generate in the North America regionThis incident is now resolved and all exports done in the North America region should work as expected. Thank you for your patience and apologize for the incovenience. | 58 min | Resolved |
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 UserZoom 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 UserZoom 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 UserZoom 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 UserZoom outage in this window ran 18h 40m, against a mean recovery of 7h 31m. If you depend on UserZoom 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.