115.69.232.0/22
At a glance
Addresses
/22 block
Visibility
79 of 80 vantage points
RPKI
Registry
JPAllocated 23rd July 2008
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 AS16625seen on 153,437 paths from 83 vantage points
- Peer of AS20940seen on 302 paths from 141 vantage points
- Peer of AS131976seen on 585 paths from 142 vantage points
- Peer of AS55391seen on 271 paths from 29 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
US
NLOne 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
- Singapore1662520940131976553918966132337This path
- Oregon, US166252094013197655391693920130Shown above
- London, UK166252094013197655391249712998529This path
- Sao Paulo16625209401319765539124973356266213This path
- Amsterdam166252094013197655391249717434549213151This 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
99%
Seen by 79 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
- Japan
- Allocated
- 23rd July 2008
- Allocation block
- 115.69.232.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 |
|---|---|---|
| 115.69.232.0/22 | AS16625 | /22 |
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
- AS1662512th 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 115.69.232.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.