89.126.216.0/22
At a glance
Addresses
/22 block
Visibility
76 of 76 vantage points
RPKI
Registry
UZAllocated 8th March 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS202660seen on 1,688 paths from 139 vantage points
- Peer of AS8193seen on 1,923 paths from 139 vantage points
- Peer of AS28910seen on 12,502 paths from 133 vantage points
- Peer of AS205103seen on 22 paths from 2 vantage points
- Peer of AS4230seen on 56,132 paths from 6 vantage points
DE
BR
FROne 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
- Amsterdam2026608193289102051038298This path
- London, UK202660819328910123898529This path
- Sao Paulo202660819328910205103423035280Shown above
- Singapore20266081932891012389693923673This path
- Oregon, US20266081932891012389855142013This 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 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
- Uzbekistan
- Allocated
- 8th March 2006
- Allocation block
- 89.126.208.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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS20266015th October 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.126.216.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.