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 2 hr ago. Last stored result reached it in 85 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 191 ms | 0 |
| Mon 22 | 0 | 0.0 | 147 ms | 0 |
| Tue 00 | 0 | 0.0 | 136 ms | 0 |
| Tue 02 | 0 | 0.0 | 79 ms | 0 |
| Tue 04 | 0 | 0.0 | 69 ms | 0 |
| Tue 06 | 0 | 0.0 | 127 ms | 0 |
| Tue 09 | 0 | 0.0 | 191 ms | 0 |
| Tue 11 | 0 | 0.0 | 142 ms | 0 |
| Tue 13 | 0 | 0.0 | 113 ms | 0 |
| Tue 15 | 0 | 0.0 | 202 ms | 0 |
| Tue 17 | 0 | 0.0 | 101 ms | 0 |
| Tue 20 | 0 | 0.0 | 124 ms | 0 |
| Tue 22 | 0 | 0.0 | 195 ms | 0 |
| Wed 00 | 0 | 0.0 | 62 ms | 0 |
| Wed 02 | 0 | 0.0 | 134 ms | 0 |
| Wed 05 | 0 | 0.0 | 65 ms | 0 |
| Wed 07 | 0 | 0.0 | 126 ms | 0 |
| Wed 09 | 0 | 0.0 | 134 ms | 0 |
| Wed 11 | 0 | 0.0 | 49 ms | 0 |
| Wed 14 | 0 | 0.0 | 143 ms | 0 |
| Wed 16 | 0 | 0.0 | 186 ms | 0 |
| Wed 18 | 0 | 0.0 | 136 ms | 0 |
| Wed 20 | 0 | 0.0 | 185 ms | 0 |
| Wed 22 | 0 | 0.0 | 58 ms | 0 |
| Wed 23 | 0 | 0.0 | 229 ms | 0 |
| Thu 02 | 0 | 0.0 | 159 ms | 0 |
| Thu 04 | 0 | 0.0 | 114 ms | 0 |
| Thu 06 | 0 | 0.0 | 538 ms | 0 |
| Thu 08 | 0 | 0.0 | 233 ms | 0 |
| Thu 10 | 0 | 0.0 | 81 ms | 0 |
| Thu 12 | 0 | 0.0 | 167 ms | 0 |
| Thu 14 | 0 | 0.0 | 231 ms | 0 |
| Thu 16 | 0 | 0.0 | 156 ms | 0 |
| Thu 18 | 0 | 0.0 | 60 ms | 0 |
| Thu 20 | 0 | 0.0 | 112 ms | 0 |
| Thu 22 | 0 | 0.0 | 51 ms | 0 |
| Fri 00 | 0 | 0.0 | 143 ms | 0 |
| Fri 02 | 0 | 0.0 | 97 ms | 0 |
| Fri 04 | 0 | 0.0 | 71 ms | 0 |
| Fri 06 | 0 | 0.0 | 66 ms | 0 |
| Fri 08 | 0 | 0.0 | 185 ms | 0 |
| Fri 11 | 0 | 0.0 | 499 ms | 0 |
| Fri 12 | 0 | 0.0 | 58 ms | 0 |
| Fri 14 | 0 | 0.0 | 81 ms | 0 |
| Fri 16 | 0 | 0.0 | 79 ms | 0 |
| Fri 17 | 0 | 0.0 | 13 ms | 0 |
| Fri 18 | 0 | 0.0 | 101 ms | 0 |
| Fri 20 | 0 | 0.0 | 85 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 Podchaser 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 Podchaser goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Podchaser alerts to Slack, Discord or a webhook — free.
We track Podchaser (podchaser.com) as part of the Entertainment group. Search millions of podcasts to uncover reach, demographics, contacts, credits, sponsors, and more. Perfect for media buying, PR campaigns, and monitoring.
Podchaser publishes an official status page at status.podchaser.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 116 ms average, 13–499 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Podchaser incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
116 ms on average over the last 24 hours (13–499 ms).
Yes, at https://status.podchaser.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 Podchaser here at once, the problem is on Podchaser'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 Podchaser. 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.