User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / News
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 1 hr ago. Last stored result reached it in 87 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 10 | 0 | 0.0 | 100 ms | 0 |
| Mon 12 | 0 | 0.0 | 112 ms | 0 |
| Mon 14 | 0 | 0.0 | 92 ms | 0 |
| Mon 16 | 0 | 0.0 | 84 ms | 0 |
| Mon 18 | 0 | 0.0 | 104 ms | 0 |
| Mon 20 | 0 | 0.0 | 154 ms | 0 |
| Mon 22 | 0 | 0.0 | 62 ms | 0 |
| Tue 01 | 0 | 0.0 | 100 ms | 0 |
| Tue 03 | 0 | 0.0 | 106 ms | 0 |
| Tue 05 | 0 | 0.0 | 127 ms | 0 |
| Tue 07 | 0 | 0.0 | 84 ms | 0 |
| Tue 09 | 0 | 0.0 | 133 ms | 0 |
| Tue 11 | 0 | 0.0 | 83 ms | 0 |
| Tue 13 | 0 | 0.0 | 140 ms | 0 |
| Tue 16 | 0 | 0.0 | 378 ms | 0 |
| Tue 18 | 0 | 0.0 | 105 ms | 0 |
| Tue 20 | 0 | 0.0 | 99 ms | 0 |
| Tue 22 | 0 | 0.0 | 95 ms | 0 |
| Wed 01 | 0 | 0.0 | 104 ms | 0 |
| Wed 03 | 0 | 0.0 | 324 ms | 0 |
| Wed 05 | 0 | 0.0 | 92 ms | 0 |
| Wed 07 | 0 | 0.0 | 115 ms | 0 |
| Wed 10 | 0 | 0.0 | 161 ms | 0 |
| Wed 12 | 0 | 0.0 | 136 ms | 0 |
| Wed 14 | 0 | 0.0 | 115 ms | 0 |
| Wed 16 | 0 | 0.0 | 149 ms | 0 |
| Wed 18 | 0 | 0.0 | 104 ms | 0 |
| Wed 20 | 0 | 0.0 | 145 ms | 0 |
| Wed 23 | 0 | 0.0 | 93 ms | 0 |
| Thu 01 | 0 | 0.0 | 55 ms | 0 |
| Thu 03 | 0 | 0.0 | 123 ms | 0 |
| Thu 05 | 0 | 0.0 | 80 ms | 0 |
| Thu 07 | 0 | 0.0 | 185 ms | 0 |
| Thu 09 | 0 | 0.0 | 90 ms | 0 |
| Thu 11 | 0 | 0.0 | 130 ms | 0 |
| Thu 13 | 0 | 0.0 | 130 ms | 0 |
| Thu 15 | 0 | 0.0 | 94 ms | 0 |
| Thu 17 | 0 | 0.0 | 118 ms | 0 |
| Thu 19 | 0 | 0.0 | 93 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 22 | 0 | 0.0 | 84 ms | 0 |
| Fri 00 | 0 | 0.0 | 185 ms | 0 |
| Fri 02 | 0 | 0.0 | 104 ms | 0 |
| Fri 04 | 0 | 0.0 | 84 ms | 0 |
| Fri 06 | 0 | 0.0 | 113 ms | 0 |
| Fri 08 | 0 | 0.0 | 85 ms | 0 |
| Fri 10 | 0 | 0.0 | 47 ms | 0 |
| Fri 12 | 0 | 0.0 | 87 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 PressReader 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 PressReader goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PressReader alerts to Slack, Discord or a webhook — free.
We track PressReader (pressreader.com) as part of the News group. Digital newsstand featuring 7000+ of the world’s most popular newspapers & magazines. Enjoy unlimited reading on up to 5 devices with 7-day free trial.
PressReader publishes an official status page at status.pressreader.com; when we can read it, its incident level is folded into the status shown here.
Common problems for news services: news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms.
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: 103 ms average, 47–185 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public PressReader incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
103 ms on average over the last 24 hours (47–185 ms).
Yes, at https://status.pressreader.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For news services, watch for news sites and live streams slowing under breaking-news traffic, and weather alerts and radar pages failing during storms. If many people report PressReader here at once, the problem is on PressReader'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 PressReader. 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.