Data as of Nov 20, 2026

2.62.4.0/24

41 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
41
16% of its addresses · 30 days
Providers
66
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

5.3K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GloryCloud
  • HASDATA
  • HELODATA
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.62.0.0/16
since Feb 2018
AS12389Residential10,051
1 always on
PJSC Rostelecom
2.60.0.0/14
since Aug 2016
AS12389Residential47,635
542 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
2.60.0.0/14262,144RU-RTK-20101008PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAOct 8, 2010abuse@rt.ru
└ 2.62.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PAMar 29, 2011abuse@rt.ru
via RU-RTK-20101008
└ 2.62.0.0 - 2.62.47.25512,288WEBSTREAMOJSC "Rostelecom"ASSIGNED PAJul 5, 2012abuse@rt.ru
via RU-SIBNET

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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
2.62.0.0/17AS12389/17RIPERPKI valid
2.62.0.0/16AS12389/16RIPEToo specific
2.60.0.0/14AS12389/24RIPERPKI valid
IRR

Route objects on 2.62.0.0/17

OriginRegistryDescriptionMaintainerModified
AS12389 RIPERostelecom networksROSTELECOM-MNTSep 28, 2018