Data as of Nov 10, 2026

83.167.68.0/22

15 residential-proxy exits · 30 days

JSC 'ER-Telecom Holding'

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
44
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4.5K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.167.64.0/198,192RU-RAID-20040616JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAJun 16, 2004abuse@domru.ru
└ 83.167.64.0/204,096COLTEL-NETColumbia-TelecomASSIGNED PADec 8, 2023abuse@domru.ru
via RU-RAID-20040616

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
Oct 2007
Current origin since
Feb 2019 · 7.7 yr
Origin networks
2
Last change of origin
Feb 2019
Recorded history

History

Handoffs
1