Data as of Nov 18, 2026

62.183.104.0/21

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
0.39% of its addresses · 30 days
Spread
4 of 8
/24s with at least one exit
Providers
42
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.9K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • Shifter
  • Smartproxy
  • 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
62.183.0.0/1732,768RU-RTK-20021209PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PADec 9, 2002abuse@rt.ru
└ 62.183.100.0 - 62.183.115.2554,096Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PADec 24, 2003abuse@rt.ru
via RU-RTK-20021209

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
May 2005
Current origin since
Jan 2006 · 21 yr
Origin networks
2
Last change of origin
Jan 2006
Recorded history

History

Handoffs
1