Vendor reports: partial outageResolved · vendor status “resolved”Official status API
AI Study creation does not appear to be working.
Reported by UserTesting · Data & Analytics · source last read 5 min ago
- Vendor start
- Jun 11, 2026, 20:27 UTC
- Vendor's clock
- Resolved
- Jun 11, 2026, 21:12 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 46 min
- 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
Affected products and regions
- Components: Test Launch Flow.[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-06-11 21:12 UTC · summary s1, evidence 3d6dcfa11e7ba6f0
Evidence (7)
- E1UserTesting reports partial outage. (vendor) source (opens in a new tab)
- E2Vendor title: "AI Study creation does not appear to be working.". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-06-11 20:27 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Test Launch Flow. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-06-11 21:12 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Test Launch Flow
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.
- Jun 11, 2026, 20:27 UTCVendor-reported startVendor time
- Jun 11, 2026, 21:12 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.