89.221.92.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
IRAllocated 29th September 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS62442seen on 4,974 paths from 138 vantage points
- Peer of AS41881seen on 18,890 paths from 138 vantage points
- Peer of AS43754seen on 164,225 paths from 138 vantage points
- Peer of AS41689seen on 164,225 paths from 138 vantage points
- Peer of AS49666seen on 273,027 paths from 76 vantage points
- Peer of AS29049seen on 32,056 paths from 39 vantage points
- Peer of AS20764seen on 4,912 paths from 2 vantage points
AZ
RU
KHOne 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
- Amsterdam6244241881437544168949666290498298This path
- London, UK624424188143754416894966669398529This path
- Sao Paulo624424188143754416894966629049645335280This path
- Singapore6244241881437544168949666290492076423673Shown above
- Oregon, US624424188143754416894966629049855142013This 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
- Iran
- Allocated
- 29th September 2006
- Allocation block
- 89.221.80.0/20
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
- AS6244215th 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.221.92.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.