121.4.4.0/22
At a glance
Addresses
/22 block
Visibility
57 of 80 vantage points
RPKI
Registry
CNAllocated 16th May 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS45090seen on 66,225 paths from 138 vantage points
- Peer of AS58466seen on 93,501 paths from 141 vantage points
- Peer of AS4134seen on 10 paths from 1 vantage point
- Peer of AS58299seen on 25,347 paths from 2 vantage points
- Peer of AS41051seen on 25,385 paths from 2 vantage points
CH
DEOne 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, UK1322038529This path
- Singapore132203132337This path
- Sao Paulo450905846641343356266213This path
- Oregon, US45090584664134693920130This path
- Amsterdam450905846641345829941051213151Shown 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
71%
Seen by 57 of 80 full-feed vantage points
Partially propagatedObserved at 5 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
- 16th May 2006
- Allocation block
- 121.4.0.0/15
- 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 |
|---|---|---|---|
| 121.4.0.0/15 | 131k | AS45090Tencent Cloud | 79/80 |
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.
Open 121.4.4.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.