185.4.106.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
IRAllocated 26th September 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS59708seen on 391 paths from 80 vantage points
- Peer of AS51074seen on 8,469 paths from 80 vantage points
- Peer of AS43754seen on 152,403 paths from 142 vantage points
- Peer of AS41689seen on 152,403 paths from 142 vantage points
- Peer of AS49666seen on 53,320 paths from 142 vantage points
- Peer of AS5511seen on 126,941 paths from 48 vantage points
- Peer of AS2914seen on 60,369 paths from 3 vantage points
- Peer of AS8966seen on 133,632 paths from 2 vantage points
FR
US
AE
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
- Oregon, US5970851074437544168949666693920130This path
- Amsterdam5970851074437544168949666551134549213151This path
- London, UK5970851074437544168949666551112998529This path
- Sao Paulo597085107443754416894966655113356266213This path
- Singapore5970851074437544168949666551129148966→ ⋯Shown above
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 80 of 80 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
- 26th September 2012
- Allocation block
- 185.4.104.0/22
- 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.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.4.104.0/22 | 1k | AS59708Rayan Hamafza Company Public Joint Stock | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 185.4.107.0/24 | 256 | AS59708Rayan Hamafza Company Public Joint Stock | 80/80 |
History
- AS5970812th August 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 185.4.106.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.