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 September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment PressReader breaks

PressReader is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official PressReader status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), 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.

See all of them free

Component statuses may change independently during partial outages.

Recent PressReader Outages & Incidents

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

Errors loading PressReader.com and Editions+Resolved Sep 23, 2026 · 1h 6mResolved

The issue with PressReader.com and Editions+ has now been resolved. --- [2026-09-23T00:40:35.780-07:00] (monitoring) A fix has been implemented and we are monitoring the progress. --- [2026-09-22T23:41:58.574-07:00] (investigating) We are investigating errors affecting PressReader.com and Editions+. Readers may be unable to load pages. We are working to restore normal service.

Errors loading PressReader.com and Editions+Resolved Sep 8, 2026 · 14 minResolved

This incident is resolved. Between approximately 15:21 and 15:53 PDT on 8 September 2026, PressReader.com and Editions+ failed on a substantial proportion of requests, and readers were often unable to load pages. The cause was a large bulk configuration change, which caused the services holding our content entitlement configuration to reload it repeatedly and overloaded the connection to our databases. We stopped the reloads to restore service, and disabled the operation responsible the same evening. This followed a shorter disruption from the same cause earlier that afternoon, recorded separately. No data was lost or corrupted. We apologise for the disruption. --- [2026-09-14T15:48:49.539-07:00] (investigating) We have identified the cause as an internal overload triggered by a bulk configuration change, and are working to relieve it. Readers may continue to see errors on PressReader.com and Editions+. --- [2026-09-14T15:56:26.712-07:00] (investigating) We are investigating errors affecting PressReader.com and Editions+. Readers may be unable to load pages. We are working to restore normal service.

Errors loading PressReader.com and Editions+Resolved Sep 8, 2026 · -3 minResolved

This incident is resolved. Between approximately 13:58 and 14:14 PDT on 8 September 2026, PressReader.com and Editions+ websites failed on a substantial proportion of requests, and readers were often unable to load pages. The cause was a large bulk configuration change, which caused the services holding our content entitlement configuration to reload it repeatedly and overloaded the connection to our databases. Service recovered when the change paused. A second, longer disruption from the same cause followed at 15:21 and is recorded separately. No data was lost or corrupted. We apologise for the disruption.

PressReader Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a PressReader incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 899.91% average · 5 days with incidentsSep 25

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 99.96%. Response times, incident history, and SLA tracking for PressReader are available on the PulsAPI dashboard.

PressReader Status FAQ

Is PressReader down right now?

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. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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 99.96%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever PressReader changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect PressReader outages?

PulsAPI reads the official PressReader status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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 free account and subscribe to PressReader: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so PressReader plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track PressReader with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services