2404:f4c0:f002::/48
At a glance
Subnets
/48 block
Visibility
61 of 62 vantage points
RPKI
Registry
CNAllocated 13th June 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS209300seen on 61 paths from 61 vantage points
- Peer of AS142650seen on 61 paths from 61 vantage points
- Peer of AS142651seen on 61 paths from 61 vantage points
- Peer of AS142652seen on 61 paths from 61 vantage points
- Peer of AS142653seen on 61 paths from 61 vantage points
- Peer of AS142654seen on 61 paths from 61 vantage points
- Peer of AS142655seen on 61 paths from 61 vantage points
- Peer of AS142656seen on 61 paths from 61 vantage points
- Peer of AS142657seen on 61 paths from 61 vantage points
- Peer of AS142658seen on 61 paths from 61 vantage points
- Peer of AS142659seen on 61 paths from 61 vantage points
AUOne path, hop by hop, from the origin outward to the vantage point that saw it. The real path runs on past the last hop shown; only the hops nearest the origin are drawn. 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
- Amsterdam209300142650142651142652142653142654142655142656→ ⋯This path
- London, UK209300142650142651142652142653142654142655142656→ ⋯Shown above
- Sao Paulo209300142650142651142652142653142654142655142656→ ⋯This path
- Singapore209300142650142651142652142653142654142655142656→ ⋯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
98%
Seen by 61 of 62 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
- APNIC — Asia-Pacific
- Country
- China
- Allocated
- 13th June 2019
- Allocation block
- 2404:f4c0::/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.
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 |
|---|---|---|---|
| 2404:f4c0:f000::/44 | 1M × /64 | AS209300Wende Tan | 37/62 |
| 2404:f4c0:f000::/44 | 1M × /64 | AS24239TWD2 Education and Research Network | 25/62 |
| 2404:f4c0::/32 | 4.3B × /64 | AS24144Wuhan LSHIY Network Technology Co., Ltd. | 61/62 |
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
- AS20930012th August 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.