162.4.97.0/24
At a glance
Addresses
/24 block
Visibility
68 of 80 vantage points
RPKI
Registry
INAllocated 9th May 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS151364seen on 68 paths from 68 vantage points
- Peer of AS45820seen on 10,122 paths from 142 vantage points
- Peer of AS9498seen on 184,654 paths from 67 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
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
- London, UK1513644582094988529This path
- Oregon, US151364458209498693920130Shown above
- Sao Paulo15136445820949864533356262355266213This path
- Singapore151364458209498645367628966132337This path
- Amsterdam151364458209498645368305829941051213151This 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
85%
Seen by 68 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
- India
- Allocated
- 9th May 2026
- Allocation block
- 162.4.97.0/24
- 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 |
|---|---|---|
| 162.4.97.0/24 | AS151364 | /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 |
|---|---|---|---|
| 162.4.96.0/24 | 256 | AS154669PT Azvi Multi Teknologi | 80/80 |
History
- AS15136412th 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 162.4.97.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.