2605:9cc0:3b3::/48
At a glance
Subnets
/48 block
Visibility
10 of 63 vantage points
RPKI
Registry
USAllocated 31st January 2020
AS paths to this prefix
No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.
Route visibility
16%
Seen by 10 of 63 full-feed vantage points
Seen by few vantage pointsObserved at 1 of our collectors.
What this percentage counts
The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.
It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.
Registry and RPKI
- RIR
- ARIN — North America
- Country
- United States
- Allocated
- 31st January 2020
- Allocation block
- 2605:9cc0::/32
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS216647th November 2026 — present
- AS2166415th October 2026 — 15th October 2026
- AS2166413th October 2026 — 13th October 2026
- AS165095th October 2026 — 5th October 2026
- AS165095th October 2026 — 5th October 2026
- AS1650929th September 2026 — 4th October 2026
- AS1650927th September 2026 — 28th September 2026
- AS1650926th September 2026 — 27th September 2026
Why these dates start where they do
A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.
Routing data derived from RouteViews MRT archives and public registry data.