- Level
- confirmed
- Worst impact
- Degraded
- Components
- Live
What to do
Check whether you use Wistia Live. 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-05-28 15:36 UTC and 2026-05-28 15:36 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: 1 hour and 6 minutes Affected Components: Live May 28, 16:43:14 GMT+0 - Resolved - Connection errors and latency have been resolved and we observe recovery across live webinars. We are continuing to monitor. May 28, 15:54:07 GMT+0 - Monitoring - Mitigations have been applied to re-route traffic away from the affected region and we are observing recovery. We are continuing to monitor progress towards full recovery. May 28, 15:36:50 GMT+0 - Investigating - We are currently investigating this incident.
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-a23be72e3f
Is Wistia still down?
No, this incident was resolved 2026-05-28 15:36 UTC. For Wistia's live state, see https://down.guide/wistia.
How long did it last?
0m, from 2026-05-28 15:36 UTC to 2026-05-28 15:36 UTC, by the times Wistia posted.
What was affected?
Wistia named Live.
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.