Data as of Nov 6, 2026
80.246.240.0/20
20 residential-proxy exits · 30 daysJSC 'ER-Telecom Holding'
Residential-proxy exits
Proxy exits
20
0.49% of its addresses · 30 days
Always-on exits
3
15% of its exits
Spread
11 of 16
/24s with at least one exit
Providers
56
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
6.0K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.246.246.0/24 | 1 | 2 | |
| 80.246.252.0/24 | 1 | 2 | |
| 80.246.250.0/24 | 1 | 1 | |
| 80.246.254.0/24 | 0 | 4 | |
| 80.246.245.0/24 | 0 | 3 | |
| 80.246.244.0/24 | 0 | 2 | |
| 80.246.249.0/24 | 0 | 2 | |
| 80.246.241.0/24 | 0 | 1 | |
| 80.246.243.0/24 | 0 | 1 | |
| 80.246.251.0/24 | 0 | 1 | |
| 80.246.255.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- GSocks
- Geonix
- Geonode
- GonzoProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- LemonPrime
- LightningProxies
- MangoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- Proxies.fo
- Proxio
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- Proxyma
- PuraRoute
- RainProxy
- ResiProxies
- Shifter
- Smartproxy
- StrikeProxy
- 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 |
|---|---|---|---|---|---|---|
| 80.246.240.0/20 | 4,096 | RU-RAID-20051019 | JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RU | ALLOCATED PA | Dec 28, 2023 | abuse@ |
| └ 80.246.240.0/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.240.64/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.240.128/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.240.192/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.241.0/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.241.64/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.241.128/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.241.192/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.242.0/26 | 64 | CLIENTS-Engelsa_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.242.64/26 | 64 | CLIENTS-Engelsa_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.242.128/26 | 64 | CLIENTS-Engelsa_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.242.192/26 | 64 | CLIENTS-Engelsa_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.243.0/26 | 64 | CLIENTS-9line_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.243.64/26 | 64 | CLIENTS-9line_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.243.128/26 | 64 | CLIENTS-9line_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.243.192/26 | 64 | CLIENTS-9line_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.244.0/26 | 64 | CLIENTS-Obuh_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.244.64/26 | 64 | CLIENTS-Obuh_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.244.128/26 | 64 | CLIENTS-Obuh_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.244.192/26 | 64 | CLIENTS-Obuh_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.245.0/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.245.64/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.245.128/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.245.192/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.246.0/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.246.64/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.246.128/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.246.192/26 | 64 | CLIENTS-Leninskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.247.0/26 | 64 | TELROS-TELECOM-CORE-1 | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.247.64/26 | 64 | TELROS-TELECOM-CORE-2 | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.247.128/26 | 64 | TELROS-TELECOM-CORE-3 | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.247.192/26 | 64 | TELROS-TELECOM-CORE-4 | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.248.0/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.248.64/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.248.128/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.248.192/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.249.0/26 | 64 | CLIENTS-Dom_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.249.64/26 | 64 | CLIENTS-Dom_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.249.128/26 | 64 | CLIENTS-Dom_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.249.192/26 | 64 | CLIENTS-Dom_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.250.0/26 | 64 | CLIENTS-Medikov_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.250.64/26 | 64 | CLIENTS-Medikov_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.250.128/26 | 64 | CLIENTS-Medikov_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.250.192/26 | 64 | CLIENTS-Medikov_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.251.0/26 | 64 | CLIENTS-Kazanskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.251.64/26 | 64 | CLIENTS-Kazanskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.251.128/26 | 64 | CLIENTS-Kazanskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.251.192/26 | 64 | CLIENTS-Kazanskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.252.0/26 | 64 | CLIENTS-Botkinskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.252.64/26 | 64 | CLIENTS-Botkinskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.252.128/26 | 64 | CLIENTS-Botkinskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.252.192/26 | 64 | CLIENTS-Botkinskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.253.0/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.253.64/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.253.128/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.253.192/26 | 64 | CLIENTS-B_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.254.0/26 | 64 | CLIENTS-Magnitigorskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.254.64/26 | 64 | CLIENTS-Magnitigorskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.254.128/26 | 64 | CLIENTS-Magnitigorskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.254.192/26 | 64 | CLIENTS-Magnitigorskaya_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.255.0/26 | 64 | CLIENTS-Levashovskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.255.64/26 | 64 | CLIENTS-Levashovskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.255.128/26 | 64 | CLIENTS-Levashovskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
| └ 80.246.255.192/26 | 64 | CLIENTS-Levashovskiy_ | Direct-Telecom | ASSIGNED PA | Nov 16, 2011 | abuse@ via RU-RAID-20051019 |
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
AS41733
RU
- Name
- JSC 'ER-Telecom Holding'
- Type
- Internet provider
- Registered
- Oct 16, 2006
- Domain
- interzet.ru
- Website
- www.interzet.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Rotating
- First seen
- Nov 2005
- Current origin since
- Dec 2024 · 1.9 yr
- Origin networks
- 2
- Last change of origin
- Dec 2024
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 80.
246. 240. 0/ 20 - Netname
- RU-RAID-20051019
- Registrant
- JSC "ER-Telecom Holding"
- Registrant country
- RU
- Organization
- JSC "ER-Telecom Holding" (ORG-RA21-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 28, 2023
- Updated
- Dec 28, 2023
- Maintainer
- RAID-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 19, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse@
domru. ru - Name
- ER-Telecom ISP Contact Role
- Handle
- RAID1-RIPE