LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

80.246.240.0/20

20 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
this exact prefix
No RPKI
Announced by
AS41733
Type
Business

Residential-proxy exits

Proxy exits
20
0.49% of its addresses · 30 days
Always-on exits
1
5.0% of its exits
Spread
11 of 16
/24s with at least one exit
Providers
55
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

6.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.246.252.0/2412
80.246.254.0/2404
80.246.245.0/2403
80.246.244.0/2402
80.246.246.0/2402
80.246.249.0/2402
80.246.241.0/2401
80.246.243.0/2401
80.246.250.0/2401
80.246.251.0/2401
80.246.255.0/2401

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
  • GhostConnect
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • StrikeProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.246.240.0/204,096RU-RAID-20051019JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PADec 28, 2023abuse@domru.ru
└ 80.246.240.0/2664CLIENTS-B_Kazachiy_9-5Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.240.64/2664CLIENTS-B_Kazachiy_9-6Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.240.128/2664CLIENTS-B_Kazachiy_9-7Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.240.192/2664CLIENTS-B_Kazachiy_9-8Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.241.0/2664CLIENTS-B_Posadskaya_9-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.241.64/2664CLIENTS-B_Posadskaya_9-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.241.128/2664CLIENTS-B_Posadskaya_9-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.241.192/2664CLIENTS-B_Posadskaya_9-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.242.0/2664CLIENTS-Engelsa_29-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.242.64/2664CLIENTS-Engelsa_29-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.242.128/2664CLIENTS-Engelsa_29-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.242.192/2664CLIENTS-Engelsa_29-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.243.0/2664CLIENTS-9line_VO_34-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.243.64/2664CLIENTS-9line_VO_34-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.243.128/2664CLIENTS-9line_VO_34-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.243.192/2664CLIENTS-9line_VO_34-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.244.0/2664CLIENTS-Obuh_Oborony_120-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.244.64/2664CLIENTS-Obuh_Oborony_120-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.244.128/2664CLIENTS-Obuh_Oborony_120-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.244.192/2664CLIENTS-Obuh_Oborony_120-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.245.0/2664CLIENTS-Leninskiy_139-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.245.64/2664CLIENTS-Leninskiy_139-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.245.128/2664CLIENTS-Leninskiy_139-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.245.192/2664CLIENTS-Leninskiy_139-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.246.0/2664CLIENTS-Leninskiy_139-5Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.246.64/2664CLIENTS-Leninskiy_139-6Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.246.128/2664CLIENTS-Leninskiy_139-7Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.246.192/2664CLIENTS-Leninskiy_139-8Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.247.0/2664TELROS-TELECOM-CORE-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.247.64/2664TELROS-TELECOM-CORE-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.247.128/2664TELROS-TELECOM-CORE-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.247.192/2664TELROS-TELECOM-CORE-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.248.0/2664CLIENTS-B_Sampsonievskiy_68-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.248.64/2664CLIENTS-B_Sampsonievskiy_68-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.248.128/2664CLIENTS-B_Sampsonievskiy_68-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.248.192/2664CLIENTS-B_Sampsonievskiy_68-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.249.0/2664CLIENTS-Dom_4-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.249.64/2664CLIENTS-Dom_4-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.249.128/2664CLIENTS-Dom_4-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.249.192/2664CLIENTS-Dom_4-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.250.0/2664CLIENTS-Medikov_5-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.250.64/2664CLIENTS-Medikov_5-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.250.128/2664CLIENTS-Medikov_5-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.250.192/2664CLIENTS-Medikov_5-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.251.0/2664CLIENTS-Kazanskaya_7-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.251.64/2664CLIENTS-Kazanskaya_7-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.251.128/2664CLIENTS-Kazanskaya_7-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.251.192/2664CLIENTS-Kazanskaya_7-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.252.0/2664CLIENTS-Botkinskaya_15-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.252.64/2664CLIENTS-Botkinskaya_15-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.252.128/2664CLIENTS-Botkinskaya_15-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.252.192/2664CLIENTS-Botkinskaya_15-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.253.0/2664CLIENTS-B_Morskaya_18-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.253.64/2664CLIENTS-B_Morskaya_18-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.253.128/2664CLIENTS-B_Morskaya_18-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.253.192/2664CLIENTS-B_Morskaya_18-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.254.0/2664CLIENTS-Magnitigorskaya_17-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.254.64/2664CLIENTS-Magnitigorskaya_17-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.254.128/2664CLIENTS-Magnitigorskaya_17-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.254.192/2664CLIENTS-Magnitigorskaya_17-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.255.0/2664CLIENTS-Levashovskiy_13-1Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.255.64/2664CLIENTS-Levashovskiy_13-2Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.255.128/2664CLIENTS-Levashovskiy_13-3Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
via RU-RAID-20051019
└ 80.246.255.192/2664CLIENTS-Levashovskiy_13-4Direct-TelecomASSIGNED PANov 16, 2011abuse@domru.ru
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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