Data as of Nov 12, 2026

86.62.64.0/18

81 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
81
0.49% of its addresses · 30 days
Always-on exits
2
2.5% of its exits
Spread
34 of 64
/24s with at least one exit
Providers
79
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

20K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • 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
86.62.64.0/1816,384RU-RAID-20050607JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAAug 24, 2020abuse@domru.ru
└ 86.62.64.0/24256MKRSEL2K7-INSCInternational Nuclear Security CenterASSIGNED PAMar 18, 2014abuse@domru.ru
via RU-RAID-20050607
└ 86.62.65.0 - 86.62.123.25515,104RINET-SOHO-86-62-NETSOHO networks segmentASSIGNED PANov 10, 2020abuse@domru.ru
via RU-RAID-20050607
└ 86.62.124.0/24256RINET-INTERNALCronyx Plus Ltd.ASSIGNED PAMar 23, 2007abuse@domru.ru
via RU-RAID-20050607
└ 86.62.125.0/24256RINET-INTERNALCronyx Plus Ltd.ASSIGNED PAMar 23, 2007abuse@domru.ru
via RU-RAID-20050607
└ 86.62.126.64/2732RINET-GGC2-NETGoogle Global Cache ClusterASSIGNED PAMay 17, 2017abuse@domru.ru
via RU-RAID-20050607
└ 86.62.126.192/2664RINET-GGC-NETGoogle Global Cache ClusterASSIGNED PAMay 17, 2017abuse@domru.ru
via RU-RAID-20050607
└ 86.62.127.0/24256RINET-INT-86-62-127Cronyx Plus Ltd.ASSIGNED PAJan 18, 2011abuse@domru.ru
via RU-RAID-20050607

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
Rotating
First seen
Jun 2005
Current origin since
Aug 2025 · 1.3 yr
Origin networks
2
Last change of origin
Aug 2025
Recorded history

History

Handoffs
1