iPaper Outage History

33 incidents recorded over the last 365 days, 24 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 iPaper status99.96% uptime history

Every Recorded iPaper Incident

iPaper incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 8, 2026Slow Flipbooks requestsThis incident has been resolved.1h 33mResolved
Oct 8, 2026Flipbooks currently unavailable due to caching issueThis incident has been resolved.2 minResolved
Oct 8, 2026Scheduled security maintenance (Horizon)The scheduled maintenance has been completed.2h 0mScheduled
Oct 7, 2026Scheduled security maintenance (Flipbooks)The scheduled maintenance has been completed.2h 0mScheduled
Sep 24, 2026Upgrading caching instancesThe scheduled maintenance has been completed.1h 0mScheduled
Sep 17, 2026Networking issue is causing some requests to failThis incident has been resolved.31 minResolved
Sep 14, 2026Seeing some requests getting timeoutsThis has been resolved, we are still investigating the root cause of this with our vendors.31 minResolved
Sep 13, 2026Networking outage## Summary We recently implemented stability fixes for an ongoing issue with our VXLAN, where the IPsec protocol occasionally desynchronizes and causes one-way loss of communication between nodes. These fixes exposed…15 minResolved
Sep 8, 2026Core networking maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Sep 8, 2026Partial outage of flipbooks## Summary Due to an ongoing issue with our VXLAN where the IPsec protocol sometimes desynchronizes causing nodes to loose communication one way, we saw all servers having issues communicating properly with other…-609 minResolved
Sep 5, 2026Partial outage of flipbooks## Summary Due to an ongoing issue with our VXLAN where the IPsec protocol sometimes desynchronizes causing nodes to loose communication one way, we saw all servers having issues communicating properly with other…42 minResolved
Sep 4, 2026Unable to serve flipbooks## Summary Due to an ongoing issue with our VXLAN where the IPsec protocol sometimes desynchronizes causing nodes to loose communication one way, we saw all servers having issues communicating properly with other…19 minResolved
Sep 2, 2026Degraded flipbooks performance## Summary We are seeing some degraded performance across flipbooks and we have identified the issue to be a networking issue, we are working with our sub-providers on a permanent fix ## Impact We were seeing some…21 minResolved
Aug 31, 2026Viewer unable to serve all requests## Summary Due to an ongoing issue with our VXLAN where the IPsec protocol sometimes desynchronizes causing nodes to loose communication one way, we saw all servers having issues communicating properly with other…58 minResolved
Aug 27, 2026Flipbooks viewer is down## Summary One of our nodes had a small milliseconds networking outage, which caused the IPsec connection used for our VXLAN between the node and another node to get out of sync. The node which lost connection was…2h 14mResolved
Aug 26, 2026Some Flipbook processing jobs were failing when using certain enrichment automation features## Summary A bug in our vendors software with IPv6 internal DNS resolution, caused us to be unable to resolve our own as well as branded domains internally. ## Impact Some services like flipbooks processing, relies…-3525 minResolved
Aug 26, 2026Failed to serve flipbooks due to caching issue## Summary During the migration we saw flipbooks failing to be served to end users, we quickly discovered this was a misconfigured cache that was not the correct size, which caused it to fill up and stop serving…-3529 minResolved
Aug 26, 2026Backend API and shop integration breaking change**Incorrect date, time and number formatting in the Backend API and shop integrations** **Summary** During a planned migration of our application servers on 24 August 2026 \(04:00–08:00 CEST\), dates, times and…-3044 minResolved
Aug 25, 2026Scheduled maintenance: Infrastructure migration of FlipbooksWe're migrating Flipbooks to a new EU-owned and -operated infrastructure. This will strengthen GDPR compliance and improve reliability of our services. You can learn more <a…4h 0mScheduled
Aug 24, 2026Issue with branded domains starting with www## Summary Branded domains starting with www or that do not have HTTPs enabled were incorrectly redirected to their apex domains, and forcebly from HTTP to HTTPs, which our applications then redirected back to HTTP…1h 11mResolved
Aug 24, 2026Scheduled maintenance: Infrastructure migration of FlipbooksThe scheduled maintenance has been completed.4h 0mScheduled
Aug 19, 2026Horizon outageDue to a faulty update from one of our infrastructure vendors our Load Balancers were unable to serve traffic for around 8 minutes while a deployment was being released that should have had zero downtime. We are…-189 minResolved
Aug 7, 2026Some branded domains are not working with SSLConfiguration has been corrected across all branded domains and no longer seeing any errors.39 minResolved
Jul 22, 2026Degraded performance for composite imagesThis incident has been resolved.3h 10mResolved
Jul 13, 2026Sporadic slow page loads in horizonMarking this as resolved as there has been no more slowdowns observed6h 5mResolved
Jul 2, 2026Unable to issue branded domain SSL due to provider outageProvider has resolved their issues and our SSL issuance has been resumed.12h 50mResolved
Jul 2, 2026Experiencing missing page images from CDNWe are no longer seeing any issues with missing images and closing this incident.23h 1mResolved
May 13, 2026Horizon admin is unavailable and the leaflet viewer is partially down.## Summary On 2026-05-13 at 06:09 UTC, a scheduled maintenance routine inadvertently deleted the Horizon production database, causing a full system outage. Our team identified the issue and restored the database from…1h 18mResolved
May 8, 2026Infrastructure MigrationThe scheduled maintenance has been completed.3h 30mScheduled
Feb 20, 2026Issues with publishing leaflets and campaignsThe publishing issue has been fully resolved. Our third-party provider deployed a fix, and we have not experienced any related issues since implementation. During the outage, our team worked on enhancing our system's…115h 51mResolved
Feb 20, 2026Domain migrationThe scheduled maintenance has been completed.3h 0mScheduled
Jan 18, 2026Admin slowWe have not experienced any more slowdowns over the past 24 hours and consider issue mitigated.44h 56mResolved
Nov 15, 2025Database migrationThe scheduled maintenance has been completed.7h 0mScheduled

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 iPaper 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 iPaper 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 iPaper 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 iPaper outage in this window ran 4d 19h, against a mean recovery of 8h 43m. If you depend on iPaper 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.