Data as of Nov 13, 2026

62.183.112.0/22

24 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
24
2.3% of its addresses · 30 days
Always-on exits
1
4.2% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
52
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
62.183.113.0/24110
62.183.115.0/2409
62.183.112.0/2405

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
62.183.112.0/23
since Nov 2019
AS12389Residential15
1 always on
PJSC Rostelecom
62.183.115.0/24
since Nov 2019
AS12389Residential9PJSC Rostelecom

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