Data as of Nov 22, 2026

62.183.115.0/24

7 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
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
40
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPFly
  • Infatica
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.183.112.0/22
since Jan 2006
AS35177Residential23
2 always on
PJSC 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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2019
Current origin since
Nov 2019 · 7.0 yr
Origin networks
1