80.71.232.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
Allocated 7th June 2001
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 AS218316seen on 451 paths from 139 vantage points
- Peer of AS198037seen on 1,171 paths from 138 vantage points
- Peer of AS199524seen on 5,484 paths from 133 vantage points
- Peer of AS174seen on 156,544 paths from 1 vantage point
- Peer of AS8551seen on 1,076,486 paths from 1 vantage point
One 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
- Amsterdam2183161980371995248298This path
- London, UK21831619803719952412998529This path
- Sao Paulo218316198037199524645335280This path
- Singapore218316198037199524349123673This path
- Oregon, US218316198037199524174855142013Shown 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
Italy
- Allocated
- 7th June 2001
- Allocation block
- 80.71.224.0/20
- 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.
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.71.233.0/24 | 256 | AS214143SKYDIGITAL TELECOM LTD | 76/76 |
History
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.71.232.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.