Data as of Nov 7, 2026
185.64.228.0/22
125 residential-proxy exits · 30 daysLLC 'Trans Analitica'
Residential-proxy exits
Proxy exits
125
12% of its addresses · 30 days
Always-on exits
42
34% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
80
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
71K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 185.64.229.0/24 | 36 | 91 | |
| 185.64.230.0/24 | 6 | 31 | |
| 185.64.228.0/24 | 0 | 2 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GoProxies
- GonzoProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- PrivateProxy
- Proxies.fo
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
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.64.228.0/22 | 1,024 | RU-TRANSAN-20140724 | LLC "Trans Analitica" (ORG-LA760-RIPE) · RU | ALLOCATED PA | Jul 24, 2014 | DShatskikh@ |
| └ 185.64.228.0/28 | 16 | NU-SRV-8 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.228.32/27 | 32 | NU-USR-NAT-4 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.228.64/26 | 64 | NU-USR-WHITE-1 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.228.128/25 | 128 | NU-USR-UL-WHITE-1 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.229.0/28 | 16 | NU-SRV-9 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.229.32/27 | 32 | NU-USR-NAT-1 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.229.64/27 | 32 | NU-USR-WHITE-2 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.229.128/25 | 128 | NU-USR-UL-WHITE-2 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.230.0/27 | 32 | NU-VIDEOMON | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.230.32/27 | 32 | NU-USR-NAT-5 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.230.64/27 | 32 | NU-USR-WHITE-4 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.230.128/25 | 128 | NU-USR-UL-WHITE-3 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.231.0/26 | 64 | NU-CORE | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.231.64/26 | 64 | NU-USR-WHITE-3 | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.231.128/27 | 32 | NU-USR-NAT-2 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.231.160/27 | 32 | NU-USR-NAT-3 | unknown | ASSIGNED PA | Nov 9, 2022 | DShatskikh@ via RU-TRANSAN-20140724 |
| └ 185.64.231.248/29 | 8 | NU-USR-INFOCOM | unknown | ASSIGNED PA | Jul 22, 2016 | DShatskikh@ via RU-TRANSAN-20140724 |
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
Origin network
AS62130
RU
- Name
- LLC 'Trans Analitica'
- Type
- Internet provider
- Registered
- Jan 31, 2014
- Domain
- cnetvrn.ru
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Sep 2014
- Current origin since
- Sep 2014 · 12 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS62130 | RIPE | LLC "Trans Analitica" | TRANSAN-MNT | Dec 9, 2015 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 185.64.228.0/24 | AS62130 | RIPE | TRANSAN-MNT | Jun 23, 2020 | |
| 185.64.229.0/24 | AS62130 | RIPE | TRANSAN-MNT | Jun 23, 2020 | |
| 185.64.230.0/24 | AS62130 | RIPE | TRANSAN-MNT | Jun 23, 2020 | |
| 185.64.231.0/24 | AS62130 | RIPE | TRANSAN-MNT | Jun 23, 2020 |
Whois
Registration for this announcement
- Range
- 185.
64. 228. 0/ 22 - Netname
- RU-TRANSAN-20140724
- Registrant
- LLC "Trans Analitica"
- Registrant country
- RU
- Organization
- LLC "Trans Analitica" (ORG-LA760-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jul 24, 2014
- Updated
- Jan 27, 2021
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jul 24, 2014
- Status
- assigned
Report abuse
Abuse contact
- DShatskikh@
cnetvrn. ru - Name
- Abuse Contact
- Handle
- AC28152-RIPE