176.111.120.0/21
At a glance
Addresses
/21 block
Visibility
79 of 80 vantage points
RPKI
Registry
PLAllocated 12th March 2012
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 AS198935seen on 265 paths from 79 vantage points
- Peer of AS9002seen on 12,631 paths from 36 vantage points
- Peer of AS6939seen on 975,334 paths from 1 vantage point
GB
USOne 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, UK19893590028529This path
- Singapore1989359002132337This path
- Sao Paulo19893590023356266213This path
- Oregon, US1989359002693920130Shown above
- Amsterdam1989359002645334549213151This 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Poland
- Allocated
- 12th March 2012
- Allocation block
- 176.111.120.0/21
- Status
- assigned
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 176.111.120.0/22 | 1k | AS198935CYBERNET WMW Sp. z o.o. | 80/80 |
| 176.111.124.0/23 | 512 | AS198935CYBERNET WMW Sp. z o.o. | 80/80 |
| 176.111.126.0/23 | 512 | AS198935CYBERNET WMW Sp. z o.o. | 80/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 176.111.112.0/21 | 2k | AS57978Digi Com ISP Radoslaw Sikora | 80/80 |
History
- AS19893512th 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 176.111.120.0/21 in the calculator/21 reference
Routing data derived from RouteViews MRT archives and public registry data.