2602:ff03:c85::/48
At a glance
Subnets
/48 block
Visibility
6 of 64 vantage points
RPKI
Registry
USAllocated 27th January 2026
AS paths to this prefix
One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.
- London, UK20473174129935280This path
- Sao Paulo20473174129935280This path
- Amsterdam20473174129912732478582838298This path
Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.
Route visibility
9%
Seen by 6 of 64 full-feed vantage points
Seen by few vantage pointsObserved at 3 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
- 27th January 2026
- Allocation block
- 2602:ff03::/36
- 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
- AS2047312th November 2026 — present
- AS204737th November 2026 — 7th November 2026
- AS204731st November 2026 — 1st November 2026
- AS2047330th October 2026 — 30th October 2026
- AS2047329th October 2026 — 29th October 2026
- AS2047327th October 2026 — 28th October 2026
- AS2047326th October 2026 — 27th October 2026
- AS2047323rd October 2026 — 24th October 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.