Critical incident

iPaper: Horizon admin is unavailable and the leaflet viewer is partially down.

May 13, 2026, 06:58 UTC
started
08:16 UTC
resolved
1 h 19 min
duration

Affected: Viewer, Admin

Current status of iPaper: Operational — live iPaper status

Timeline

  1. May 13, 2026, 06:58 UTC
    identified
    We're current seeing an outage on our database server. This affects the ability to login to the administration, and results in leaflets not loading as they should. We're working hard to get the system back online again. We apologize for this disturbance.
  2. May 13, 2026, 07:14 UTC
    monitoring
    Database is back online and we're monitoring
  3. May 13, 2026, 08:16 UTC
    resolved
    Admin and Viewer are performing as expected. We do not expect further downtime.
  4. May 13, 2026, 08:17 UTC
    postmortem
    ## 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 the most recent available backup. Horizon was brought back online at 07:04 UTC, resulting in approximately 55 minutes of downtime. The restored backup was from 05:15 UTC, which means all data created or modified between 05:15 UTC and 06:09 UTC \(approximately 54 minutes\) has been permanently lost. No data was lost during the downtime window itself, as the system was inaccessible during that period. ## Root Cause We made a mistake. This incident occurred in the context of our ongoing infrastructure migration from AWS to Cycle, which we are undertaking to move our hosting from the US to the EU for improved data locality and compliance. During this migration, a scheduled maintenance routine was not properly adapted to the new environment, causing it to delete the production database instead of performing its intended operation. We take full responsibility for this error. ## How are we preventing this from happening again The faulty routine has been immediately disabled. We are now auditing all scheduled routines in the new environment to ensure nothing similar can occur. Beyond that, we are implementing safeguards to prevent automated deletion of production databases. We sincerely apologize for the disruption and data loss. If you believe you are affected, please reach out to our customer care team and we will do our best to assist you.

Updates as published by iPaper (original).

Other services with incidents at the same time

More iPaper incidents