169.197.116.0/24
At a glance
Addresses
/24 block
Visibility
17 of 80 vantage points
RPKI
Registry
USAllocated 28th December 2016
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS520022seen on 17 paths from 17 vantage points
- Peer of AS137280seen on 1,400 paths from 142 vantage points
- Peer of AS21859seen on 2,738 paths from 126 vantage points
- Peer of AS12389seen on 26,029 paths from 1 vantage point
- Peer of AS4766seen on 70,419 paths from 2 vantage points
HK
RU
KR
SGOne 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
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
21%
Seen by 17 of 80 full-feed vantage points
Seen by few vantage pointsObserved at 4 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
- United States
- Allocated
- 28th December 2016
- Allocation block
- 169.197.96.0/19
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 169.197.116.0/23 | 512 | AS137280Kingsoft cloud corporation limited | 80/80 |
| 169.197.116.0/22 | 1k | AS21859Zenlayer Inc | 80/80 |
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
- AS52002212th 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 169.197.116.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.