Data as of Nov 9, 2026
185.190.120.0/22
3 residential-proxy exits · 30 daysJoint Stock Company 'Medsi group'
Residential-proxy exits
Proxy exits
3
0.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
25
selling exits here
Oct 10, 2026 – Nov 8, 2026
Exits seen per day
1.6K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 185.190.120.0/24 | 0 | 1 | |
| 185.190.121.0/24 | 0 | 1 | |
| 185.190.122.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 9Proxy
- BirdProxies
- BottingTools
- Byteful
- Evomi
- FloppyData
- Geonode
- GonzoProxy
- IPFly
- Infatica
- InfiniteProxies
- NovaProxy
- Novada
- PrivateProxy
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyWing
- Proxyma
- PuraRoute
- Shifter
- Smartproxy
- Thordata
- VantageProxies
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 185.190.120.0/23 since Jan 2018 | AS206295 | Business | 2 | Joint Stock Company "Medsi group" | |
| 185.190.120.0/24 since Jan 2018 | AS206295 | Business | 1 | Joint Stock Company "Medsi group" | |
| 185.190.121.0/24 since Jan 2018 | AS206295 | Business | 1 | Joint Stock Company "Medsi group" | |
| 185.190.122.0/23 since Jan 2018 | AS206295 | Business | 1 | Joint Stock Company "Medsi group" | |
| 185.190.122.0/24 since Jan 2018 | AS206295 | Business | 1 | Joint Stock Company "Medsi group" | |
| 185.190.123.0/24 since Jan 2018 | AS206295 | Business | Joint Stock Company "Medsi group" |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 185.190.120.0/22 | 1,024 | RU-MEDSI-GROUP-20170216 | Joint Stock Company "Medsi group" (ORG-JSCG2-RIPE) · RU | ALLOCATED PA | Feb 16, 2017 | abuse@ |
| └ 185.190.120.32/31 | 2 | RU-MEDSI-GROUP-UK | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.34/31 | 2 | RU-MEDSI-GROUP-MSK4 | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.36/31 | 2 | RU-MEDSI-GROUP-MSK7 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.38/31 | 2 | RU-MEDSI-GROUP-MSK8 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.40/31 | 2 | RU-MEDSI-GROUP-MSK9 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.42/31 | 2 | RU-MEDSI-GROUP-MSK11 | unknown | ASSIGNED PA | May 29, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.44/31 | 2 | RU-MEDSI-GROUP-MSK12 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.46/31 | 2 | RU-MEDSI-GROUP-MSK14 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.48/31 | 2 | RU-MEDSI-GROUP-MSK15 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.50/31 | 2 | RU-MEDSI-GROUP-MSK16 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.96/31 | 2 | RU-MEDSI-GROUP-Perm1 | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.120.104/31 | 2 | RU-MEDSI-GROUP-Nyagan | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.32/31 | 2 | RU-MEDSI-GROUP-UK | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.34/31 | 2 | RU-MEDSI-GROUP-MSK4 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.36/31 | 2 | RU-MEDSI-GROUP-MSK7 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.38/31 | 2 | RU-MEDSI-GROUP-MSK8 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.40/31 | 2 | RU-MEDSI-GROUP-MSK9 | unknown | ASSIGNED PA | May 28, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.42/31 | 2 | RU-MEDSI-GROUP-MSK11 | unknown | ASSIGNED PA | May 29, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.44/31 | 2 | RU-MEDSI-GROUP-MSK12 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.46/31 | 2 | RU-MEDSI-GROUP-MSK14 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.48/31 | 2 | RU-MEDSI-GROUP-MSK15 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.50/31 | 2 | RU-MEDSI-GROUP-MSK16 | unknown | ASSIGNED PA | Aug 24, 2020 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.96/31 | 2 | RU-MEDSI-GROUP-Perm1 | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
| └ 185.190.122.104/31 | 2 | RU-MEDSI-GROUP-Nyagan | unknown | ASSIGNED PA | Apr 30, 2019 | abuse@ via RU-MEDSI-GROUP-20170216 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2017
- Current origin since
- May 2017 · 9.5 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS206295 | RIPE | RU-MEDSI-GROUP-1-MNT | Feb 21, 2017 |
Whois
Registration for this announcement
- Range
- 185.
190. 120. 0/ 22 - Netname
- RU-MEDSI-GROUP-20170216
- Registrant
- Joint Stock Company "Medsi group"
- Registrant country
- RU
- Organization
- Joint Stock Company "Medsi group" (ORG-JSCG2-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Feb 16, 2017
- Updated
- Feb 21, 2017
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 16, 2017
- Status
- assigned
Report abuse
Abuse contact
- abuse@
medsigroup. ru - Name
- Abuse-C Role
- Handle
- AR39256-RIPE