Live / iPaper / Incident
iPaper: Flipbooks unable to serve some requests
iPaper · ipaper.ioMajor incidentResolved2026-11-14 01:09 UTC
Public — what happened
Summary
iPaper said that some requests for its flipbooks could not be served, and it rated the incident as major. The company began investigating at 23:50 UTC on 13 November 2026 and reported at 00:04 UTC that it had found the problem and was working on a fix. At 00:41 UTC iPaper said its upstream DNS provider had been causing timeouts when looking up hostnames, that it had moved to a different DNS provider, and that requests were being served normally again. The incident was marked resolved at 01:09 UTC on 14 November.
Affected
Viewer, Admin, Backend API, Pop-ups
Timeline
- Started — 2026-11-13 23:50 UTC
- Investigating — 2026-11-13 23:50 UTC
- Identified — 2026-11-14 00:04 UTC
- Monitoring — 2026-11-14 00:41 UTC
- Resolved — 2026-11-14 01:09 UTC · 1h 19m 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 47, 2026, our weekly internet health report.