Vendor reports: degradedResolved · vendor status “resolved”Official status API

UserTesting interface running slow

Reported by UserTesting · Data & Analytics · source last read just now

Vendor start
Jan 22, 2026, 16:32 UTC
Vendor's clock
Resolved
Jan 23, 2026, 16:45 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 0 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • UserTesting reports degraded: "UserTesting interface running slow".[E1, E2]
  • The vendor marked it resolved at 2026-01-23 16:45 UTC.[E3, E7]

Affected products and regions

  • Components: Dashboard, Study Results, Insights Summary.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-01-23 16:45 UTC · summary s1, evidence 28eb2dfa3fa72f27

Evidence (7)
  1. E1UserTesting reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "UserTesting interface running slow". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-01-22 16:32 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Dashboard, Study Results, Insights Summary. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-23 16:45 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Dashboard, Study Results, Insights Summary

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

UserTesting is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jan 22, 2026, 16:32 UTCVendor-reported startVendor time
  2. Jan 23, 2026, 16:45 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.

UserTesting: UserTesting interface running slow — statuswall