- Level
- confirmed
- Worst impact
- Degraded
- Components
- Encoding
- Down Index
- 10of 100
What to do
Check whether you use Wistia Encoding. 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-04-08 14:44 UTC and 2026-04-08 14:44 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: 30 minutes Affected Components: Encoding Apr 8, 15:13:57 GMT+0 - Resolved - This incident has been resolved. Apr 8, 14:51:01 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 8, 14:44:03 GMT+0 - Investigating - We are currently investigating this incident - thanks for your patience.
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-2eed8fead8
Is Wistia still down?
No, this incident was resolved 2026-04-08 14:44 UTC. For Wistia's live state, see https://down.guide/wistia.
How long did it last?
0m, from 2026-04-08 14:44 UTC to 2026-04-08 14:44 UTC, by the times Wistia posted.
What was affected?
Wistia named Encoding.
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.