PressReader Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live PressReader status99.37% uptime history

Every Recorded PressReader Incident

PressReader incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 28, 2026Errors loading Editions+ (App/Website Affected)This incident has been resolved.4h 5mResolved
Sep 23, 2026Errors loading PressReader.com and Editions+The issue with PressReader.com and Editions+ has now been resolved.1h 6mResolved
Sep 8, 2026Errors loading PressReader.com and Editions+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…14 minResolved
Sep 8, 2026Errors loading PressReader.com and Editions+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…-3 minResolved
Aug 24, 2026Articles, text view and For You unavailableThis incident is resolved. Between approximately 03:40 and 05:27 PDT on 24 August 2026, articles and text view failed to open and the personalised For You feed was slow or unavailable. Our websites and apps remained…1h 3mResolved
Aug 20, 2026Page images slow or failing to loadThis incident is resolved. Between approximately 15:44 and 20:26 PDT on 20 August 2026, page images on our websites were slow or failed to load, with older back issues more affected than recently released editions. The…3h 55mResolved
Aug 20, 2026Articles, text view and For You unavailableThis incident is resolved. Between approximately 23:27 PDT on 19 August and 01:52 PDT on 20 August 2026, articles and text view failed to open and the personalised For You feed was slow or unavailable. Our websites and…5 minResolved
Aug 20, 2026Publication processing delaysThis incident is resolved. Between approximately 19:08 and 20:47 PDT on 19 August 2026, delays in our publication processing pipeline meant newly released editions took longer than usual to become available. The cause…1h 37mResolved
Jul 27, 2026Catalog API unavailable to partner integrationsAn expired TLS certificate on our public API endpoint left partners with platform integrations unable to call our Catalog API from approximately 13:00 PDT on 26 July until service was restored at approximately 06:00 PDT…0 minResolved
Jul 27, 2026Catalog API unavailable to partner integrationsThis incident is resolved. Partners with platform integrations were unable to call our Catalog API from approximately 13:00 PDT on 26 July until approximately 06:00 PDT on 27 July, following the expiry of the TLS…4h 47mResolved
Jul 26, 2026PressReader.com unavailableThis incident is resolved. pressreader.com was unavailable from 14:03 to 14:18 PDT on 26 July. The cause was an expired TLS certificate on the public API endpoint the website depends on. No data was lost, corrupted or…14 minResolved
Jul 8, 2026Editions+ URL link/re-directThis incident has been resolved.4h 22mResolved
Jun 8, 2026Disruption to sign-in, payments and content loadingSummary ‌ 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…3h 34mResolved
Apr 22, 2026Reduced-resolution pages on PressReader.com & Editions+Summary ‌ On 22 April 2026, between approximately 08:02 and 11:07 PDT, some text and pages on [PressReader.com](http://PressReader.com) and Editions\+ websites were displayed in reduced resolution for a limited number…3h 5mResolved
Apr 14, 2026TECHNICAL STATUSThe issue has been resolved.3 minResolved
Apr 9, 2026Platform disruption — payments, sign-in & content loadingSummary ‌ On 9 April 2026, between approximately 10:46 and 11:50 PDT, our platform experienced a service disruption lasting about one hour. A database connectivity issue under high load caused intermittent failures…1h 3mResolved
Mar 25, 2026TECHNICAL STATUSThis incident has now been resolved as of 18:10 PST, and all impacted services have been restored to normal operation. We will continue to closely monitor system performance to ensure sustained stability. Thank you for…0 minResolved
Feb 18, 2026Possible Downloading DelaysThe issue with [technical problem] has now been resolved.59 minResolved
Feb 10, 2026XML processing delaysThis incident has been resolved.1h 16mResolved
Jan 27, 2026Print Articles IssueThis incident has been resolved.5h 7mResolved
Dec 31, 2025hub.pressreader.com returns processing errorThis incident has been resolved.2h 56mResolved
Dec 28, 2025Technical StatusPlease be advised that the previous technical issue with some pages not loading on Pressreader.com and Branded edition sites has been resolved. PressReader Technical Team41 minResolved
Dec 10, 2025TECHNICAL STATUSThis incident has been resolved.37 minResolved
Dec 5, 2025Service Disruption Caused by Upstream ProviderThe issue with our upstream service provider has been resolved, and our operations are now back to normal. Thank you for your patience while we worked to address the problem.-519 minResolved
Nov 24, 2025TECHNICAL STATUSThis incident has been resolved.2h 15mResolved
Nov 20, 2025TECHNICAL STATUSThis incident has been resolved.14 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next PressReader incident opens instead, at the point where knowing still changes what you do.

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

How to Read This PressReader Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before PressReader acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single PressReader outage in this window ran 5h 7m, against a mean recovery of 1h 48m. If you depend on PressReader in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.