89.251.22.0/23
At a glance
Addresses
/23 block
Visibility
81 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 Singapore.
Seen from Singapore
- Peer of AS61317seen on 13,535 paths from 144 vantage points
- Peer of AS29802seen on 19,822 paths from 145 vantage points
- Peer of AS3257seen on 331,260 paths from 28 vantage points
- Peer of AS9002seen on 52,591 paths from 2 vantage points
US
GB
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
- Amsterdam61317298023257250918298This path
- London, UK61317298023257291435280This path
- Sao Paulo61317298023257645335280This path
- Singapore613172980232579002132337Shown above
- Oregon, US613172980232572335220130This 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 81 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
- 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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 89.251.22.0/24 | 256 | AS63023GTHost | 80/81 |
| 89.251.23.0/24 | 256 | AS60707Kapteyan Bilisim Teknolojileri Sanayi ve Ticaret A.S | 81/81 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS6131722nd September 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 89.251.22.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.