23.162.28.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
THAllocated 3rd August 2026
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 AS402829seen on 80 paths from 80 vantage points
- Peer of AS138997seen on 302 paths from 142 vantage points
- Peer of AS58955seen on 6,056 paths from 142 vantage points
- Peer of AS45629seen on 1,054 paths from 125 vantage points
- Peer of AS5511seen on 63,365 paths from 45 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
HK
FR
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
- Amsterdam4028291389975895545629551134549213151This path
- London, UK4028291389975895545629551112998529This path
- Sao Paulo402829138997589554562955113356266213Shown above
- Singapore402829138997589554562955111299132337This path
- Oregon, US40282913899758955456295511693920130This 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
- ARIN — North America
- Country
- Thailand
- Allocated
- 3rd August 2026
- Allocation block
- 23.162.28.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 |
|---|---|---|
| 23.162.28.0/24 | AS402829 | /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
No prefix of the same length in the same parent block is announced.
History
- AS40282912th 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 23.162.28.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.