Kindle Unlimited page reads, explained

When a reader borrows your book through Kindle Unlimited and turns pages, you earn for each page actually read (Amazon calls these KENP pages). The money comes out of a monthly KU fund that's split among all pages read by all readers that month — so the per-page rate rises and falls from month to month. Royalties, KU included, are paid out roughly 60 days after the end of each month.

A borrow only counts when the reader opens the book and starts turning pages. Someone downloading your book and never reading it earns nothing. That's why a borrow count can look healthy while page reads lag behind — and why a borrowed-but-unread pile-up shows up later, if it shows up at all.

Reporting lag. Page reads are not real-time. They update on Amazon's schedule and can trail behind actual reading by hours or longer, so a flat day can simply be a slow report, not vanished readers.

Reader drop-off. Reads depend on how far into the book people get. A cohort of readers stopping at the same point — a slow chapter, a formatting hiccup — bends the curve without any change on Amazon's side.

Visibility shifts. KU reads track borrows, and borrows track how visible the book is on Amazon. Algorithm changes and category shifts move reads the same way they move sales.

The month boundary. Borrowing and payout cycles are monthly, so reads often move in monthly waves rather than a straight line.

One quiet day isn't a signal. The pattern that matters is a dip that lasts several days and is echoed by other authors at the same time — that points to an Amazon-side change rather than your book. If you're the only one seeing it, check whether your book is still enrolled in KU, whether an ad campaign changed, and whether you're comparing against a promo spike rather than your baseline.

The Dip Detector board tracks both sales and page reads, so a KU-wide dip shows up as a cluster of "down" reports in the same window. Why do Amazon and KU sales dip? covers the common causes in more depth.