Skip to main content
Wistia

Media Processing slowed and Media.Ready Webhooks not firing

Degraded Lasted 0m · started · Wistia's page

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-07-27 19:30 UTC and 2026-07-27 19:30 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

  1. resolved

    Type: Incident Duration: 19 hours and 30 minutes Affected Components: Encoding Jul 28, 15:00:00 GMT+0 - Resolved - We identified and resolved a config issue that prevented updates from being pushed from our encoding system to our main app. The system has both a push and pull mechanism for getting encoding updates, but with only the pull updates encoding appeared slower and the media.ready webhooks were not firing. After resolving the config issue, we ensured that all uploads during the affected period were synced properly to reflect the correct encoding status. We've taken additional steps to prevent this issue from reoccurring and improved monitoring around those status updates to prevent similar incidents in the future. Jul 27, 19:30:00 GMT+0 - Investigating - We're seeing a slowdown in encoding being marked as ready and webhooks for media.ready not firing.

    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-9b680cc6cd

Is Wistia still down?

No, this incident was resolved 2026-07-27 19:30 UTC. For Wistia's live state, see https://down.guide/wistia.

How long did it last?

0m, from 2026-07-27 19:30 UTC to 2026-07-27 19:30 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.