2001:dc7:ffc3::/48
China Internet Network Infomation CenterAS24406
China Internet Network Infomation CenterAS24151
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
38 of 62 vantage points
RPKI
Registry
CNAllocated 13th September 2004
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS24151seen on 643 paths from 133 vantage points
- Peer of AS1280seen on 50 paths from 20 vantage points
- Peer of AS6762seen on 284,000 paths from 4 vantage points
US
ITOne 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, UK244062185951907This path
- Singapore2415121859132337This path
- Amsterdam24406330716939213151This path
- Sao Paulo241511280676232590Shown 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
61%
Seen by 38 of 62 full-feed vantage points
Partially 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
- APNIC — Asia-Pacific
- Country
- China
- Allocated
- 13th September 2004
- Allocation block
- 2001:dc7::/32
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2001:dc7::/32 | 4.3B × /64 | AS24151China Internet Network Infomation Center | 60/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2001:dc7:ffc2::/48 | 65.5k × /64 | AS24151China Internet Network Infomation Center | 20/62 |
| 2001:dc7:ffc2::/48 | 65.5k × /64 | AS24406China Internet Network Infomation Center | 40/62 |
History
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.