- Level
- confirmed
- Worst impact
- Degraded
- Components
- Transcripts
- Down Index
- 10of 100
What to do
Check whether you use Wistia Transcripts. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-08-07 15:24 UTC and 2026-08-07 15:24 UTC may need a replay.Subscribe to Wistia's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=wistia works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Wistia 1
- resolved
Type: Incident Duration: 4 hours and 49 minutes Affected Components: Transcripts Aug 7, 20:13:22 GMT+0 - Resolved - This incident has been resolved. Aug 7, 15:58:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 7, 15:24:03 GMT+0 - Identified - We have identified the issue and will be deploying a fix shortly.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-61790912fc
Is Wistia still down?
No, this incident was resolved 2026-08-07 15:24 UTC. For Wistia's live state, see https://down.guide/wistia.
How long did it last?
0m, from 2026-08-07 15:24 UTC to 2026-08-07 15:24 UTC, by the times Wistia posted.
What was affected?
Wistia named Transcripts.
What caused it?
Wistia hasn't published a root cause. If it does, it shows here.
Where does this come from?
Wistia's official status page, https://status.wistia.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.