89.251.25.0/24
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
UAAllocated 24th August 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Adjacentseen on 286 paths from 143 vantage points
- Adjacentseen on 59 paths from 30 vantage points
- Peer of AS132372seen on 763 paths from 84 vantage points
- Peer of AS38182seen on 143 paths from 1 vantage point
MY
US
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
- Singapore21920630058132337This path
- London, UK21920630058291435280This path
- Sao Paulo21920630058645335280This path
- Amsterdam21920630058132372381828298Shown above
- Oregon, US2192063005829142335220130This 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 80 of 81 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
- Ukraine
- Allocated
- 24th August 2006
- Allocation block
- 89.251.16.0/20
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 89.251.25.0/24 | AS219206 | /24 |
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.251.24.0/24 | 256 | AS973Revive IT Solutions LLC | 80/81 |
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.251.25.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.