80.71.147.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
AEAllocated 23rd September 2021
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS48107seen on 80 paths from 80 vantage points
- Peer of AS56740seen on 2,583 paths from 141 vantage points
- Peer of AS12406seen on 43,413 paths from 142 vantage points
- Peer of AS60280seen on 24,523 paths from 63 vantage points
- Peer of AS12389seen on 526,463 paths from 116 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
BY
RU
US
DEOne 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, UK481075674012406602808529This path
- Amsterdam48107567401240660280123896939213151Shown above
- Sao Paulo4810756740124066028090023356266213This path
- Singapore48107567401240660280123894766132337This path
- Oregon, US4810756740124066028012389693920130This 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 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
- United Arab Emirates
- Allocated
- 23rd September 2021
- Allocation block
- 80.71.147.0/24
- 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 |
|---|---|---|---|
| 80.71.146.0/24 | 256 | AS48259Marcin Zalewski trading as MK2 | 80/80 |
History
- AS4810712th 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 80.71.147.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.