User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 59 min ago. Last stored result reached it in 663 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 747 ms | 0 |
| Mon 23 | 0 | 0.0 | 704 ms | 0 |
| Tue 01 | 0 | 0.0 | 384 ms | 0 |
| Tue 03 | 0 | 0.0 | 378 ms | 0 |
| Tue 05 | 0 | 0.0 | 353 ms | 0 |
| Tue 07 | 0 | 0.0 | 854 ms | 0 |
| Tue 10 | 0 | 0.0 | 371 ms | 0 |
| Tue 12 | 0 | 0.0 | 732 ms | 0 |
| Tue 14 | 0 | 0.0 | 459 ms | 0 |
| Tue 16 | 0 | 0.0 | 735 ms | 0 |
| Tue 18 | 0 | 0.0 | 383 ms | 0 |
| Tue 21 | 0 | 0.0 | 341 ms | 0 |
| Tue 23 | 0 | 0.0 | 660 ms | 0 |
| Wed 01 | 0 | 0.0 | 478 ms | 0 |
| Wed 03 | 0 | 0.0 | 497 ms | 0 |
| Wed 06 | 0 | 0.0 | 364 ms | 0 |
| Wed 08 | 0 | 0.0 | 214 ms | 0 |
| Wed 10 | 0 | 0.0 | 388 ms | 0 |
| Wed 12 | 0 | 0.0 | 632 ms | 0 |
| Wed 15 | 0 | 0.0 | 761 ms | 0 |
| Wed 17 | 0 | 0.0 | 712 ms | 0 |
| Wed 19 | 0 | 0.0 | 197 ms | 0 |
| Wed 21 | 0 | 0.0 | 776 ms | 0 |
| Wed 23 | 0 | 0.0 | 423 ms | 0 |
| Thu 02 | 0 | 0.0 | 543 ms | 0 |
| Thu 04 | 0 | 0.0 | 508 ms | 0 |
| Thu 06 | 0 | 0.0 | 421 ms | 0 |
| Thu 08 | 0 | 0.0 | 685 ms | 0 |
| Thu 10 | 0 | 0.0 | 731 ms | 0 |
| Thu 12 | 0 | 0.0 | 767 ms | 0 |
| Thu 14 | 0 | 0.0 | 679 ms | 0 |
| Thu 16 | 0 | 0.0 | 368 ms | 0 |
| Thu 18 | 0 | 0.0 | 540 ms | 0 |
| Thu 20 | 0 | 0.0 | 676 ms | 0 |
| Thu 22 | 0 | 0.0 | 664 ms | 0 |
| Fri 00 | 0 | 0.0 | 384 ms | 0 |
| Fri 02 | 0 | 0.0 | 425 ms | 0 |
| Fri 04 | 0 | 0.0 | 701 ms | 0 |
| Fri 06 | 0 | 0.0 | 697 ms | 0 |
| Fri 08 | 0 | 0.0 | 368 ms | 0 |
| Fri 10 | 0 | 0.0 | 636 ms | 0 |
| Fri 11 | 0 | 0.0 | 466 ms | 0 |
| Fri 13 | 0 | 0.0 | 696 ms | 0 |
| Fri 15 | 0 | 0.0 | 757 ms | 0 |
| Fri 17 | 0 | 0.0 | 469 ms | 0 |
| Fri 19 | 0 | 0.0 | 723 ms | 0 |
| Fri 21 | 0 | 0.0 | 988 ms | 0 |
| Fri 23 | 0 | 0.0 | 663 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Wowza yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Wowza goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wowza alerts to Slack, Discord or a webhook — free.
Wowza, at wowza.com, is one of the Entertainment services we monitor. Build mission critical video streaming infrastructure with flexible video server solutions for live and on demand streaming. Deploy on prem, cloud, edge, or air gapped environments with secure, low latency delivery.
Wowza publishes an official status page at status.wowza.com; when we can read it, its incident level is folded into the status shown here.
Common problems for entertainment services: streams buffering or not starting, playback errors, and app sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 582 ms average, 19–988 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Wowza incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
582 ms on average over the last 24 hours (19–988 ms).
Yes, at https://status.wowza.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Wowza here at once, the problem is on Wowza's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Wowza. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.