176.96.240.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
CZAllocated 15th August 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS43972seen on 15 paths from 15 vantage points
- Peer of AS199961seen on 1,693 paths from 140 vantage points
- Peer of AS48084seen on 2,365 paths from 77 vantage points
- Peer of AS31133seen on 11,756 paths from 97 vantage points
- Peer of AS23764seen on 6,509 paths from 2 vantage points
RU
HK
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
- Oregon, US43972199961693920130This path
- Amsterdam43972432015209162255213151This path
- London, UK43972488824750290028529This path
- Sao Paulo43972488824750290023356266213This path
- Singapore43972199961480843113323764132337Shown 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 80 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
- Czechia
- Allocated
- 15th August 2011
- Allocation block
- 176.96.224.0/19
- Status
- allocated
- 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.
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 |
|---|---|---|---|
| 176.96.241.0/24 | 256 | AS212860AIRNET llc | 80/80 |
History
- AS4397212th 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.96.240.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.