Is Wistia Down?
- Wistia's status page
- Operational · read 5 hours ago, too long ago to count
- FlareWarden checks
- Website reachable · 8 of 8 regions · 358 ms
Right now
The verdict is the worse of these two. How we decide
Wistia's status page
status.wistia.com · read · too long ago to set the verdict
| Component | Status |
|---|---|
| Group Record | Operational |
| Billing | Operational |
| Transcripts | Operational |
| Record | Operational |
| Edit | Operational |
| wistia.com the service itself | Operational |
| App | Operational |
| Uploads | Operational |
| Encoding | Operational |
| Stats | Operational |
| Embeds | Operational |
| Live | Operational |
FlareWarden checks
wistia.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 358 ms
- Checked
By region
- Chicago reachable, 110 ms
- Johannesburg reachable, 1126 ms
- London reachable, 40 ms
- Los Angeles reachable, 136 ms
- San Jose reachable, 79 ms
- Singapore reachable, 336 ms
- Sydney reachable, 844 ms
- Tokyo reachable, 198 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Chicago | 99 ms | 0 ms | 3 ms | 105 ms |
| Johannesburg | 60 ms | 160 ms | 163 ms | 626 ms |
| London | 19 ms | 1 ms | 10 ms | 34 ms |
| Los Angeles | 65 ms | 1 ms | 4 ms | 130 ms |
| San Jose | 65 ms | 1 ms | 4 ms | 74 ms |
| Singapore | 322 ms | 1 ms | 5 ms | 332 ms |
| Sydney | 151 ms | 0 ms | 3 ms | 840 ms |
| Tokyo | 36 ms | 1 ms | 3 ms | 193 ms |
History
Incidents Wistia reported
from status.wistia.com
We don't have Wistia's incident history yet.
Wistia website availability
Measured by FlareWarden · wistia.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 222ms
Last 30 days
64-day clean streakMeasured by FlareWarden's own checks of wistia.com from multiple regions every 6 hours. Wistia's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 64 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Wistia does
Wistia hosts and delivers video for marketing teams, providing embeddable players, viewer analytics, live events and lead capture inside the video itself. Businesses use it on product pages, for webinars and for gated content, so a Wistia outage is visible on customer-facing pages rather than internally. Its analytics also feed marketing systems that depend on those viewing events.
What an outage looks like
Embedded players on marketing pages show a spinner or fail to appear at all, leaving a gap in the page layout. Uploads complete but videos stay in encoding and never become playable. Live events fail to start or drop mid-broadcast, which cannot be repeated for the audience that missed it. Stats and transcripts stop updating while playback itself continues normally.
What to do about it
status.wistia.com tracks Embeds, Edit, wistia.com, Uploads, Encoding, Live, App, Stats, Group Record, Billing and Transcripts separately, so a viewer-facing failure is easy to tell from an internal one. Embeds is the row that matters when customers report a broken page. If a live event is scheduled during an incident, moving it beats starting into a degraded pipeline.
Is it down for everyone, or just you?
If this page says Wistia is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Wistia outage FAQ
Videos will not play on my site. Is it Wistia or my page?
An upload finished but the video is stuck processing. Is that an outage?
A live event is scheduled during an incident. Should I go ahead?
My video stats dropped to zero. Did viewers stop watching?
Does a Wistia outage affect videos already embedded elsewhere?
How we measure this
- We request Wistia's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Wistia publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Wistia itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.
Get alerted when Wistia goes down
We check Wistia every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring