89.106.138.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
IEAllocated 29th March 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS218641seen on 228 paths from 76 vantage points
- Peer of AS62610seen on 50,430 paths from 138 vantage points
- Peer of AS29752seen on 16,468 paths from 132 vantage points
- Peer of AS3257seen on 1,444 paths from 19 vantage points
- Peer of AS51088seen on 25,218 paths from 2 vantage points
GB
US
NL
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, UK218641626102975242298529This path
- Amsterdam21864162610297523257510888298Shown above
- Sao Paulo21864162610297523257645335280This path
- Oregon, US218641626102975232571299855142013This 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
72%
Seen by 55 of 76 full-feed vantage points
Partially propagatedObserved at 4 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
- Ireland
- Allocated
- 29th March 2006
- Allocation block
- 89.106.136.0/21
- 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 |
|---|---|---|---|
| 89.106.139.0/24 | 256 | AS51173Premier Data Networks 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 89.106.138.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.