Live / iPaper / Incident
iPaper: Slow Flipbooks requests
iPaper · ipaper.ioMajor incidentResolved2026-10-08 12:10 UTC
Public — what happened
Summary
iPaper reported a major incident on October 8, 2026, beginning at 10:36 UTC, in which requests to its flipbooks were loading slowly. About ten minutes later, the company said it had traced the problem to one of its application servers and was preparing a fix. By 10:58 UTC iPaper said the fix was in place and it was no longer seeing slow or failed requests, and the incident was marked resolved at 12:10.
Affected
Viewer, Admin, Backend API, Pop-ups
Timeline
- Started — 2026-10-08 10:36 UTC
- Investigating — 2026-10-08 10:36 UTC
- Identified — 2026-10-08 10:47 UTC
- Monitoring — 2026-10-08 10:58 UTC
- Resolved — 2026-10-08 12:10 UTC · 1h 34m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach iPaper against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for iPaper: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the iPaper report →
More from iPaper
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.