Data as of Nov 13, 2026

2.60.167.0/24

37 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
37
14% of its addresses · 30 days
Providers
50
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • GloryCloud
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.60.0.0/16
since Dec 2015
AS12389Residential10,050
39 always on
PJSC Rostelecom
2.60.0.0/14
since Aug 2016
AS12389Residential46,775
531 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.60.0.0/1665,536RU-SIBNETunknownLIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-RTK-20101008
└ 2.60.160.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@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.60.160.0/19AS12389/19RIPERPKI valid
2.60.0.0/16AS12389/16RIPEToo specific
2.60.0.0/14AS12389/24RIPERPKI valid
IRR

Route objects on 2.60.160.0/19

OriginRegistryDescriptionMaintainerModified
AS12389 RIPEROSTELECOM-MNTFeb 20, 2025