a chronology, not a dashboard
What changed for this object, and when.
Search an ASN or an IPv4 prefix. RPKI edits, visibility cliffs and state changes land on one UTC time axis, newest first, with the object's context kept beside it. Each card shows one record; consecutive records of the same kind within ten minutes are shown together with a count.
How to read it
- 01Time runs down. Newest first, grouped by UTC day, with the exact instant on every card.
- 02One card is one change. An RPKI edit, a visibility cliff, or a state record. The chip tells you which.
- 03Context is not the timeline. The side column holds the object's shape and the source names; the main column holds the chronology.
RPKI entries come from the daily diff of ROA objects and are placed at the ROA validity boundary. Visibility cliffs are five-minute episodes where collectors stopped seeing prefixes from one origin. State entries record the last time the visibility index changed its view of a prefix.
Every number is fetched live. No accounts, no cookies, no tracking.
reading the window
Fetching the chronology…
the live data did not load
No answer from the data service.
The chronology needs a live response. Check the network and try again.