2001:df2:5080::/48
At a glance
Subnets
/48 block
Visibility
41 of 63 vantage points
RPKI
Registry
INAllocated 9th December 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS138224seen on 193 paths from 117 vantage points
- Peer of AS45804seen on 6,312 paths from 139 vantage points
- Peer of AS45820seen on 159,615 paths from 138 vantage points
- Peer of AS4755seen on 1,218,738 paths from 138 vantage points
- Peer of AS6453seen on 96,172 paths from 5 vantage points
- Peer of AS25091seen on 663,519 paths from 2 vantage points
US
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
- London, UK13822445804458204755645335280This path
- Sao Paulo13822445804458204755645335280This path
- Amsterdam138224458044582047556453250918298Shown above
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
65%
Seen by 41 of 63 full-feed vantage points
Partially propagatedObserved 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
- APNIC — Asia-Pacific
- Country
- India
- Allocated
- 9th December 2019
- Allocation block
- 2001:df2:5080::/48
- Status
- assigned
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2001:df2:5080::/48 | AS138224 | /48 |
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
- AS1382249th November 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.