152.175.8.0/22
At a glance
Addresses
/22 block
Visibility
81 of 81 vantage points
RPKI
Registry
HKAllocated 23rd May 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS209554seen on 1,332 paths from 144 vantage points
- Peer of AS49304seen on 16,196 paths from 145 vantage points
- Peer of AS9516seen on 10,289 paths from 144 vantage points
- Peer of AS137409seen on 7,188 paths from 2 vantage points
EE
AU
CHOne 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, UK20955449304896635280This path
- Oregon, US20955449304693920130This path
- Amsterdam2095544930495161374098298Shown above
- Sao Paulo20955449304951613740935280This path
- Singapore2095544930495164229132337This 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 81 of 81 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
- Hong Kong SAR China
- Allocated
- 23rd May 2014
- Allocation block
- 152.175.0.0/16
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 152.175.8.0/23 | 512 | AS209554ISIF OU | 44/81 |
| 152.175.10.0/23 | 512 | AS209554ISIF OU | 45/81 |
| 152.175.8.0/24 | 256 | AS209554ISIF OU | 10/81 |
| 152.175.9.0/24 | 256 | AS209554ISIF OU | 10/81 |
| 152.175.10.0/24 | 256 | AS209554ISIF OU | 10/81 |
| 152.175.11.0/24 | 256 | AS209554ISIF OU | 10/81 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 152.175.12.0/22 | 1k | AS209554ISIF OU | 81/81 |
History
- AS20955422nd 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 152.175.8.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.