2406:e3c0::/32
CHINANET Guangdong province Guangzhou MAN networkAS134773
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/32 block
Visibility
30 of 62 vantage points
RPKI
Registry
CNAllocated 14th December 2020
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 AS137721seen on 30 paths from 30 vantage points
- Peer of AS24357seen on 692 paths from 62 vantage points
- Peer of AS23910seen on 5,200 paths from 62 vantage points
- Peer of AS23911seen on 448 paths from 20 vantage points
- Peer of AS4635seen on 8,319 paths from 24 vantage points
- Peer of AS6939seen on 335,352 paths from 8 vantage points
ID
HK
USOne 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
- Singapore137721243572391023911132337This path
- Amsterdam13772124357239102391146356939213151This path
- Sao Paulo1377212435723910239114635693932590Shown above
- London, UK137721243572391023911463569394191334288→ ⋯This 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
48%
Seen by 30 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
- 14th December 2020
- Allocation block
- 2406:e3c0::/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
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.