UserTesting Outage History

25 incidents recorded over the last 365 days, 25 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.

Live UserTesting status100.00% uptime history

Every Recorded UserTesting Incident

UserTesting incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026Tree Test and Card SortThis incident has been resolved.12h 58mResolved
Oct 21, 2026Delays in study response collectionThis incident has been resolved.22h 38mResolved
Oct 14, 2026Issues when resuming or launching studies in the platformThe incident has been resolved.1h 0mResolved
Sep 14, 2026Exports are not working for new UserTesting studiesThis incident has been resolved.15h 52mResolved
Aug 3, 2026Customers are unable to join Live Conversations with NotetakingThis incident has been resolved.3h 26mResolved
Jul 10, 2026We're investigating an issue which may cause AI Test Creation to fail for some usersThis incident has been resolved.36 minResolved
Jun 29, 2026Email notifications for scheduled live conversations are temporarily unavailable.This incident has been resolved.1h 46mResolved
Jun 17, 2026Duplicating Surveys, Interactive tests and new TOLThis incident has been resolved.3h 18mResolved
Jun 11, 2026AI Study creation does not appear to be working.This incident has been resolved.45 minResolved
May 27, 2026Some UTZ studies cannot be ordered or resumedThis incident has been resolved.9h 23mResolved
May 21, 2026Mobile login issueThis incident has been resolved.23 minResolved
May 20, 2026UserTesting dashboard chat widget is not workingThis incident has been resolved.15 minResolved
May 19, 2026Degraded Platform PerformanceThis incident has been resolved.23h 14mResolved
May 4, 2026Hidden Observers streamThis incident has been resolved.2h 3mResolved
May 1, 2026Reports of some users not being able to sign into their AccountsThis incident has been resolved.2h 20mResolved
Apr 30, 2026Issues adding an audience to a testThis incident has been resolved.2h 14mResolved
Apr 28, 2026Some studies are filling more slowly than usualThis incident has been resolved.22h 9mResolved
Apr 23, 2026Some participants are currently unable to enter tests launched from the Figma pluginThis incident has been resolved.1h 10mResolved
Mar 18, 2026Issues with our Chrome extensionsThis incident has been resolved.51h 52mResolved
Mar 10, 2026Usertesting platform down.This incident has been resolved.1h 13mResolved
Feb 20, 2026Issue IdentifiedThis incident has been resolved.234h 26mResolved
Jan 22, 2026UserTesting interface running slowThis incident has been resolved.24h 12mResolved
Nov 28, 2025Some pages under www.usertesting.com are not loading.The incident is resolved and all pages in our Marketing website www.usertesting.com should be loading as expected. Apologies for the inconvenience and thank you for your patience.7h 47mResolved
Nov 19, 2025Issues trying to load the dashboard when logging into the platformThis incident is resolved now. The dashboard should be loading correctly for all users. Apologies for the inconvenience and thank you for your patience.26 minResolved
Nov 6, 2025We're investigating reports that the dashboard is extremely slow or not loading for some usersThis incident has been resolved.1h 29mResolved

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 UserTesting 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 UserTesting 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 UserTesting 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 UserTesting outage in this window ran 9d 18h, against a mean recovery of 17h 53m. If you depend on UserTesting 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.