101.193.232.0/22
At a glance
Addresses
/22 block
Visibility
78 of 80 vantage points
RPKI
Registry
CNAllocated 24th December 2010
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 AS402279seen on 468 paths from 78 vantage points
- Peer of AS136826seen on 2,660 paths from 78 vantage points
- Peer of AS18013seen on 5,319 paths from 110 vantage points
- Peer of AS3491seen on 122,201 paths from 47 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
US
ID
HK
BROne 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, UK40227913682618013349112998529This path
- Sao Paulo4022791368261801334913356266213Shown above
- Singapore4022791368261801334914229132337This path
- Oregon, US402279136826180133491693920130This path
- Amsterdam402279136826180133491325734549213151This 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 78 of 80 full-feed vantage points
Globally 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
- 24th December 2010
- Allocation block
- 101.192.0.0/14
- 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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 101.193.236.0/22 | 1k | AS402279Geoscry Network LLC | 78/80 |
History
- AS40227912th 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.
Open 101.193.232.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.