LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

2.60.240.0/20

17 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
17
0.42% of its addresses · 30 days
Always-on exits
2
12% of its exits
Spread
8 of 16
/24s with at least one exit
Providers
64
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
2.60.246.0/2414
2.60.248.0/2414
2.60.243.0/2403
2.60.240.0/2402
2.60.242.0/2401
2.60.244.0/2401
2.60.245.0/2401
2.60.247.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
2.60.0.0/16
since Dec 2015
AS12389Residential10,656
37 always on
PJSC Rostelecom
2.60.0.0/14
since Aug 2016
AS12389Residential47,326
523 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
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.192.0/1816,384WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-SIBNET
└ 2.60.240.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.241.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.242.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.243.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.244.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.245.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.246.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.247.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.248.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.249.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.250.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.251.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.252.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.253.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.254.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 2.60.255.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2015
Current origin since
Mar 2025 · 1.6 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
1