Sources & data freshness

Snapshots describe observations at selected collectors. Missing observations do not establish that a route is absent everywhere.

Source	Snapshot	Imported	Selected peer coverage
ris-rrc00	10 Oct 16:00 UTC	10 Oct 16:34 UTC	2a00:5884::6/IPv6: 263,051 prefixes; 89.234.186.6/IPv4: 1,123,103 prefixes
routeviews2	10 Oct 18:00 UTC	10 Oct 18:37 UTC	140.192.8.16/IPv4: 1,096,800 prefixes
routeviews6	10 Oct 18:00 UTC	10 Oct 18:58 UTC	2406:840:feed:2::1/IPv6: 262,554 prefixes

Data readiness

Ready · evaluated 10 Oct 19:14 UTC

ris-rrc00 · available · age 11698 seconds
routeviews2 · available · age 4498 seconds
routeviews6 · available · age 4498 seconds

RPKI validator

available · observed 10 Oct 18:28 UTC

1018559 validated payloads; 87 publication-point issues reported by the validator. A completed generation can retain individual source limitations.

Registry cache coverage

APNIC · 2 cached resources · latest fetch 10 Oct 19:02 UTC
ARIN · 3 cached resources · latest fetch 10 Oct 18:51 UTC
RIPE NCC · 11 cached resources · latest fetch 10 Oct 18:39 UTC

Public ASN supplements

PeeringDB: operator-declared network profiles and presence, cached for 24 hours. RIPEstat history: requested 7/30-day windows, cached for one hour. Neither replaces local routing observations.

local-rpki · ready · 1 cached requests · latest successful fetch 10 Oct 18:55 UTC
peeringdb · public-limited · 6 cached requests · latest successful fetch 10 Oct 18:51 UTC
ripestat · public-limited · 2 cached requests · latest successful fetch 10 Oct 18:58 UTC

Allocation snapshot

available · observed 10 Oct 00:00 UTC

Limits

BGP freshness policy is 24 hours; validator freshness policy is two hours; allocation statistics freshness policy is three days. These are application limits, not upstream availability promises.
Registry cache coverage reflects requested resources, not a complete RIR mirror.
Collector observations do not represent every route or a traffic-weighted visibility measure.