80.173.163.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
KZAllocated 11th June 2003
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS58172seen on 3,795 paths from 138 vantage points
- Peer of AS39824seen on 5,822 paths from 85 vantage points
- Peer of AS9198seen on 119,043 paths from 135 vantage points
- Peer of AS12389seen on 413,266 paths from 105 vantage points
- Peer of AS6939seen on 358,340 paths from 2 vantage points
RU
US
KHOne 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
- Amsterdam5817235168204858298This path
- London, UK581723516890028529This path
- Sao Paulo58172351689002645335280This path
- Oregon, US581723516820485855142013This path
- Singapore5817239824919812389693923673Shown above
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 76 of 76 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Kazakhstan
- Allocated
- 11th June 2003
- Allocation block
- 80.173.160.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 |
|---|---|---|
| 80.173.163.0/24 | AS58172 | /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 |
|---|---|---|---|
| 80.173.162.0/24 | 256 | AS58172Freedom Telecom Operations LLP | 76/76 |
History
- AS5817222nd September 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 80.173.163.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.