122.200.16.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
INAllocated 11th December 2006
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 AS38310seen on 164 paths from 80 vantage points
- Peer of AS55352seen on 9,184 paths from 141 vantage points
- Peer of AS55836seen on 571,522 paths from 141 vantage points
- Peer of AS64049seen on 36,075 paths from 51 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
SG
US
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, UK383105535255836640498529This path
- Singapore38310553525583664049132337This path
- Amsterdam3831055352558366404934549213151This path
- Sao Paulo383105535255836640493356266213Shown above
- Oregon, US38310553525583664049693920130This 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
100%
Seen by 80 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
- India
- Allocated
- 11th December 2006
- Allocation block
- 122.200.16.0/21
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 122.200.16.0/24 | AS38310 | /24 |
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 |
|---|---|---|---|
| 122.200.17.0/24 | 256 | AS38310iCan Solutions Pvt. Ltd. AS | 80/80 |
History
- AS3831012th 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 122.200.16.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.