History and timeline
One timeline for registration events, transfers, routing windows and observed changes.
Every dated event about a resource lands on one timeline, in order, whatever its source.
Event categories
| Category | What it is |
|---|---|
registration | Registration of the block and changes to the record. |
allocation | Allocation events for the resource. |
transfer | RIR records of the space moving between holders or registries. |
routing | BGP visibility windows: an origin AS announcing the space over a period. |
rir | The space appearing in, moving within, or leaving a registry's published holdings. |
observed | Changes SubnetHistory detected itself. |
tag | An analyst label being applied. |
peeringdb | The network's PeeringDB record being created or updated. |
Events covering a period carry a start, an end, and an ongoing flag while the period is open.
Origin history
One row per AS that has ever originated the space.
| Column | Meaning |
|---|---|
| AS and holder | The origin network and its name. |
| Prefix | The exact prefix that AS announced. |
| Scope | Whether the prefix is the block itself, a covering block, or a more specific inside it. |
| First seen, last seen | The observed window, marked ongoing while the announcement is current. |
| Windows | How many distinct visibility windows the AS has had. |
| Peak peers | The most full BGP peers that saw the announcement, a rough measure of global visibility. |
A cell with no recorded value reads n/a, not zero. The frequent origin change tag exists for exactly that pattern.
What SubnetHistory records itself
Every lookup archives its answers, and a record differing from the previous snapshot writes a change event summarising what moved. These appear in the observed category. The raw archive, change events plus persisted routing observations, is available from the archive endpoint.
Very large timelines are trimmed, and the report states how many routing announcements were omitted.