Critical incident

PressReader: Catalog API unavailable to partner integrations

Affected: Public API

Current status of PressReader: Operational — live PressReader status

Timeline

1. Jul 27, 2026, 09:00 UTC
   investigating
   A partner has reported that calls to our Catalog API are failing. Partners with platform integrations may be unable to reach the API. We are investigating. Our websites and apps are unaffected.
2. Jul 27, 2026, 12:53 UTC
   identified
   The cause has been identified as an expired TLS certificate on our public API endpoint. Calls fail at certificate verification rather than returning data. We are moving the endpoint to a managed certificate.
3. Jul 27, 2026, 13:00 UTC
   monitoring
   The endpoint has been moved to a managed certificate and connections are succeeding again. Because the change alters the address the endpoint resolves to, recovery will reach clients progressively as DNS propagates. We are monitoring.
4. Jul 27, 2026, 13:47 UTC
   resolved
   This 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 certificate on that endpoint. Connections failed securely throughout: no traffic was served over an untrusted connection, and no data was lost, corrupted or exposed. Any integration that connects to a stored IP address rather than the hostname will need to be updated. A separate, shorter disruption to pressreader.com on 26 July arose from the same certificate and is recorded separately. Affected partners have received a full post-mortem. We apologise for the disruption.

Updates as published by PressReader (original).