Data as of Nov 16, 2026

62.183.16.0/22

1,024 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
1,024
100% of its addresses · 30 days
Always-on exits
971
95% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.7M observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
62.183.16.0/24244255
62.183.18.0/24244254
62.183.19.0/24243255
62.183.17.0/24240255

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • Kookey
  • LemonBright
  • Maskify
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Registrations in this block

The registry's network records over this block, widest first, each 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.0.0/198,192Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAFeb 4, 2005abuse@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 62.183.0.0/19

62.183.0.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1