2a0f:1cc5:6004::/48
At a glance
Subnets
/48 block
Visibility
63 of 63 vantage points
RPKI
Registry
USAllocated 22nd October 2025
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS218538seen on 63 paths from 63 vantage points
- Peer of AS204211seen on 1,960 paths from 139 vantage points
- Peer of AS206069seen on 3,432 paths from 116 vantage points
- Peer of AS216211seen on 4,837 paths from 55 vantage points
- Peer of AS6939seen on 130,681 paths from 2 vantage points
GB
CN
CHOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- Amsterdam21853820421120606921621169398298Shown above
- London, UK21853820421120606940792291435280This path
- Sao Paulo218538204211206069216211693935280This path
- Singapore2185382042112060692162116939132337This 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
100%
Seen by 63 of 63 full-feed vantage points
Globally propagatedObserved at 4 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United States
- Allocated
- 22nd October 2025
- Allocation block
- 2a0f:1cc0::/29
- 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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0f:1cc5:6005::/48 | 65.5k × /64 | AS218538ARGSMENT LIMITED | 63/63 |
History
- AS2185384th October 2026 — present
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.