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 20 min ago. Last stored result reached it in 268 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 179 ms | 0 |
| Mon 18 | 0 | 0.0 | 39 ms | 0 |
| Mon 20 | 0 | 0.0 | 353 ms | 0 |
| Mon 22 | 0 | 0.0 | 246 ms | 0 |
| Tue 00 | 0 | 0.0 | 224 ms | 0 |
| Tue 02 | 0 | 0.0 | 104 ms | 0 |
| Tue 04 | 0 | 0.0 | 307 ms | 0 |
| Tue 06 | 0 | 0.0 | 144 ms | 0 |
| Tue 09 | 0 | 0.0 | 223 ms | 0 |
| Tue 11 | 0 | 0.0 | 71 ms | 0 |
| Tue 13 | 0 | 0.0 | 160 ms | 0 |
| Tue 15 | 0 | 0.0 | 245 ms | 0 |
| Tue 17 | 0 | 0.0 | 295 ms | 0 |
| Tue 20 | 0 | 0.0 | 84 ms | 0 |
| Tue 22 | 0 | 0.0 | 229 ms | 0 |
| Wed 00 | 0 | 0.0 | 221 ms | 0 |
| Wed 02 | 0 | 0.0 | 199 ms | 0 |
| Wed 05 | 0 | 0.0 | 233 ms | 0 |
| Wed 07 | 0 | 0.0 | 244 ms | 0 |
| Wed 09 | 0 | 0.0 | 247 ms | 0 |
| Wed 11 | 0 | 0.0 | 191 ms | 0 |
| Wed 14 | 0 | 0.0 | 236 ms | 0 |
| Wed 16 | 0 | 0.0 | 245 ms | 0 |
| Wed 18 | 0 | 0.0 | 39 ms | 0 |
| Wed 20 | 0 | 0.0 | 152 ms | 0 |
| Wed 22 | 0 | 0.0 | 276 ms | 0 |
| Thu 00 | 0 | 0.0 | 284 ms | 0 |
| Thu 02 | 0 | 0.0 | 324 ms | 0 |
| Thu 05 | 0 | 0.0 | 285 ms | 0 |
| Thu 07 | 0 | 0.0 | 502 ms | 0 |
| Thu 09 | 0 | 0.0 | 253 ms | 0 |
| Thu 11 | 0 | 0.0 | 318 ms | 0 |
| Thu 13 | 0 | 0.0 | 77 ms | 0 |
| Thu 15 | 0 | 0.0 | 198 ms | 0 |
| Thu 17 | 0 | 0.0 | 81 ms | 0 |
| Thu 19 | 0 | 0.0 | 84 ms | 0 |
| Thu 21 | 0 | 0.0 | 262 ms | 0 |
| Thu 23 | 0 | 0.0 | 233 ms | 0 |
| Fri 01 | 0 | 0.0 | 243 ms | 0 |
| Fri 03 | 0 | 0.0 | 83 ms | 0 |
| Fri 05 | 0 | 0.0 | 207 ms | 0 |
| Fri 07 | 0 | 0.0 | 273 ms | 0 |
| Fri 09 | 0 | 0.0 | 233 ms | 0 |
| Fri 10 | 0 | 0.0 | 260 ms | 0 |
| Fri 11 | 0 | 0.0 | 254 ms | 0 |
| Fri 13 | 0 | 0.0 | 219 ms | 0 |
| Fri 15 | 0 | 0.0 | 283 ms | 0 |
| Fri 17 | 0 | 0.0 | 268 ms | 0 |
98.63% 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 Podscribe 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 Podscribe goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Podscribe alerts to Slack, Discord or a webhook — free.
We track Podscribe (podscribe.com) as part of the Entertainment group. Measure, verify, and prove ROI for every podcast, streaming, broadcast radio and audio ad. Smart ad targeting, incrementality testing, and competitive intel - in one platform."
Podscribe publishes an official status page at status.podscribe.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: 98.63% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 222 ms average, 83–283 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 Podscribe incident since monitoring began 8 days ago.
From our own checks: 98.63% over 8 days of checks.
222 ms on average over the last 24 hours (83–283 ms).
Yes, at https://status.podscribe.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 Podscribe here at once, the problem is on Podscribe'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 Podscribe. 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.