Major incident

PressReader: Disruption to sign-in, payments and content loading

Affected: Apps, Web sites, Apps, PressReader.com

Current status of PressReader: Operational — live PressReader status

Timeline

1. Jun 8, 2026, 12:14 UTC
   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.
2. Jun 8, 2026, 12:42 UTC
   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.
3. Jun 8, 2026, 13:50 UTC
   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.
4. Jun 8, 2026, 13:56 UTC
   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.
5. Jun 8, 2026, 14:45 UTC
   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.
6. Jun 8, 2026, 15:48 UTC
   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.
7. Jun 15, 2026, 19:02 UTC
   postmortem
   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.

Updates as published by PressReader (original).