PressReader logo

Is PressReader Down?

SaaSLive status, outages, and incident history

No. PressReader is up right now.

Every monitored PressReader system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 22m agoLive, rechecked every 60s
How we know: the official PressReader status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

PressReader Component Status

The main PressReader systems on this page. All 10 are operational right now.

10operational
Content Processing and Delivery » Content Delivery
Operational
Content Processing and Delivery » Content Processing
Operational
Editions + » Apps
Operational

7 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Editions + » Web sites, Partner Tools » Business Analytics, Partner Tools » Rich Media Tool, PressReader » Apps, PressReader » PressReader.com, Public API, Stripe API.

Create a free account

Component statuses may change independently during partial outages.

Recent PressReader Outages & Incidents

Incident history from the official PressReader status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
Pressreader.com not loadingResolved Jul 26, 2026 · 14 minResolved

This incident has been resolved. --- [2026-07-26T14:03:57.784-07:00] (investigating) Please be advised we are experiencing technical issues for the following services on our network. - Pressreader.com We are currently working on the issue and will provide an update as soon as possible.

Editions+ URL link/re-directResolved Jul 8, 2026 · 4h 22mResolved

This incident has been resolved. --- [2026-07-08T12:00:39.838-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-08T09:26:20.773-07:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-07-08T07:42:19.241-07:00] (investigating) Please be advised we are currently experiencing technical issues with our systems that is affecting multiple services. - Editions+ We are currently working on the issues and will provide an update as soon as possible.

Disruption to sign-in, payments and content loadingResolved Jun 8, 2026 · 3h 34mResolved

Summary ‌ On 8 June 2026, between approximately 03:50 and 07:17 PDT, a hardware fault in a network device at our hosting facility disrupted one of our internet connections. Services that rely on external connectivity — sign-in and authentication, payment processing, and the loading of some content and images — were affected across PressReader apps, [PressReader.com](http://PressReader.com), and Editions\+ apps and websites. The faulty device was replaced and all services recovered; the incident was then monitored for stability and formally resolved at 08:48 PDT. No data was lost or corrupted. ‌ Impact ‌ Sign-in and authentication to partner libraries were unavailable for some users. Payment processing was interrupted, affecting purchases and subscriptions. Loading of some content and images was degraded where it depended on external delivery. Some branded partner sites and learning-portal access were unavailable. No data was lost or corrupted, and some internal systems continued to operate. ‌ Timeline \(PDT\) ‌ 03:50 — Automated monitoring detected failures across externally-dependent services; investigation began. 05:14 — First status page update posted. 06:50 — Cause identified \(an unresponsive network device on one internet connection\); remediation began. 07:00–07:17 — Faulty device replaced; affected services recovered. 07:45 — Fix confirmed; services monitored for stability. 08:48 — Incident resolved. ‌ Root Cause ‌ A hardware fault in a network device disrupted one of our multiple internet connections. Because external authentication, payments and some content delivery are routed over the affected connection, those capabilities were interrupted while the device was unavailable. An attempted reset was unsuccessful, so the device was replaced with a spare unit, after which all services were restored. ‌ What We Are Doing ‌ We are implementing automatic failover for outbound traffic across our multiple internet connections so that a single device fault cannot interrupt external services. We are also evaluating inbound load-balancing, restoring the affected hardware to full redundancy with a standby unit, enhancing network-level monitoring so connectivity faults are identified faster, and expanding health monitoring of branded partner sites. ‌ Closing ‌ We apologise for the disruption. Service continuity is fundamental to the trust our partners place in us, and we are implementing the improvements above, with automatic failover as the priority. For any questions, please contact your account manager or our IT Operations team. --- [2026-06-15T15:53:29.435-07:00] (resolved) This incident is resolved. A hardware fault in a network device disrupted one of our internet connections, which affected sign-in, payments, and the loading of some content and images across PressReader apps, PressReader.com, and Editions+ apps and websites. The faulty device was replaced and all services have recovered, with no data lost or corrupted. A full post-mortem is available on the Postmortem tab. We apologise for the disruption. --- [2026-06-15T15:54:11.439-07:00] (monitoring) A fix has been implemented — the faulty network device has been replaced — and affected services have recovered. We are monitoring to confirm full stability before marking this incident resolved. --- [2026-06-15T15:54:50.442-07:00] (identified) We have traced this to a network issue affecting connectivity to some of our services and are working on a fix. The disruption is affecting PressReader apps and PressReader.com as well as Editions+ apps and websites — some users may be unable to sign in, complete payments, or load certain content. --- [2026-06-15T15:55:43.438-07:00] (identified) The issue has been identified as a network problem affecting connectivity to some of our services, and a fix is being implemented. Sign-in, payments, and the loading of some content remain affected for some users. --- [2026-06-15T15:56:58.438-07:00] (investigating) We are continuing to investigate. Sign-in, payments, and the loading of some content remain affected for some users while our teams work to identify the cause. --- [2026-06-15T15:58:06.427-07:00] (investigating) We are investigating a disruption affecting multiple services. Some users may be unable to sign in, complete payments, or load certain content and images. We are working to identify the cause and will provide updates as soon as we can.

Live PressReader Outage Reports

Problems reported by engineers using PressReader. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No PressReader problems reported yet.

Something wrong with PressReader on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About PressReader

PressReader exposes 14 monitored components on its status page at status.pressreader.com — Apps, PressReader and Content Processing among them. Follow PressReader downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured PressReader uptime at 100.00%. Response times, incident history, and SLA tracking for PressReader are available on the PulsAPI dashboard.

PressReader Status FAQ

Is PressReader down right now?

PulsAPI checks PressReader every 60 seconds. The verdict at the top of this page comes from the latest poll of the official PressReader status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if PressReader is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until PressReader recovers.

How do I check PressReader uptime history?

PulsAPI tracks PressReader uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for PressReader.

How fast does PulsAPI detect PressReader outages?

PulsAPI polls the official PressReader status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual PressReader components?

Yes. PulsAPI monitors 10 individual PressReader components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when PressReader goes down?

Yes. Create a PulsAPI account and subscribe to PressReader. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever PressReader status changes.

How do I report an issue with PressReader to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot PressReader problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor PressReader?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor PressReader alongside up to 9 other services at pulsapi.com/signup.

Track PressReader with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when PressReader status changes.

Start free trial