Data as of Nov 10, 2026
2.60.192.0/18
1 anonymizer address · <0.01% · VPN2,358 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
2,358
14% of its addresses · 30 days
Always-on exits
3
0.13% of its exits
Spread
56 of 64
/24s with at least one exit
Providers
113
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
187K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.60.224.0/24 | 1 | 46 | |
| 2.60.248.0/24 | 1 | 4 | |
| 2.60.246.0/24 | 1 | 4 | |
| 2.60.227.0/24 | 0 | 63 | |
| 2.60.211.0/24 | 0 | 61 | |
| 2.60.226.0/24 | 0 | 61 | |
| 2.60.235.0/24 | 0 | 58 | |
| 2.60.193.0/24 | 0 | 57 | |
| 2.60.199.0/24 | 0 | 57 | |
| 2.60.206.0/24 | 0 | 56 | |
| 2.60.214.0/24 | 0 | 55 | |
| 2.60.201.0/24 | 0 | 54 | |
| 2.60.192.0/24 | 0 | 54 | |
| 2.60.225.0/24 | 0 | 54 | |
| 2.60.205.0/24 | 0 | 54 | |
| 2.60.236.0/24 | 0 | 53 | |
| 2.60.198.0/24 | 0 | 52 | |
| 2.60.208.0/24 | 0 | 52 | |
| 2.60.229.0/24 | 0 | 52 | |
| 2.60.231.0/24 | 0 | 51 | |
| 2.60.232.0/24 | 0 | 50 | |
| 2.60.202.0/24 | 0 | 49 | |
| 2.60.228.0/24 | 0 | 49 | |
| 2.60.209.0/24 | 0 | 49 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HPROXY
- HideProxy
- HydraProxy
- IPFly
- IPMUSK
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
IPv4 market
Path
1 · Holder
record created Oct 8, 2010 · reallocated to a party the registry does not name Nov 2, 2010
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 2.60.192.0/18 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 1<0.01% | 1 |
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 2.60.0.0/14 since Aug 2016 | AS12389 | Residential | 47,441 542 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Anonymizer addresses | Operator | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|---|
| 2.60.192.0/19 since Jul 2020 | AS12389 | Residential | 1,541 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.224.0/20 since Jul 2020 | AS12389 | Residential | 10.02%VPN | VPN servicesoperated by VPN Gate | 799 1 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |
| 2.60.240.0/20 since Mar 2025 | AS12389 | Residential | 17 2 always on | PJSC Rostelecom via OJSC "Sibirtelecom" |
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 2.60.0.0/14 | 262,144 | RU-RTK-20101008 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Oct 8, 2010 | abuse@ |
| └ 2.60.0.0/16 | 65,536 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 2, 2010 | abuse@ via RU-RTK-20101008 |
| └ 2.60.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via RU-SIBNET |
| └ 2.60.240.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.241.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.242.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.243.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.244.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.245.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.246.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.247.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.248.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.249.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.250.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.251.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.252.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.253.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.254.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 2.60.255.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ 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.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 16,383 | >99% | 4 | |
| VPNanonymizer | 1 | <0.01% | 1 |
Network & registry
Announced by
Covering announcement 2.60.0.0/16
- Prefix
- 2.60.0.0/16
- Announced by
- AS12389 PJSC Rostelecom
- Type
- Residential
- Anonymizer addresses
- none
- Proxy exits
- 10,721
- Always-on exits
- 41
- RPKI
- RPKI valid
- Netname
- RU-SIBNET
- RIR
- RIPE NCC
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 2.
60. 0. 0/ 14 - Registration type
- ALLOCATED PA
- Record created
- Oct 8, 2010
- Reallocated to
- Not named in the registry
- Reallocated range
- 2.
60. 0. 0/ 16 - Reallocation type
- LIR-PARTITIONED PA
- Reallocated
- Nov 2, 2010
Origin network
AS12389
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 1, 2005
- Domain
- rt.ru
- Website
- www.company.rt.ru/en/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
2.60.0.0/16
Routing history
- Pattern
- Stable
- First seen
- Nov 2010
- Current origin since
- Dec 2015 · 11 yr
- Origin networks
- 2
- Last change of origin
- Dec 2015
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.60.0.0/16 | AS12389 | /16 | RIPE | RPKI valid |
| 2.60.0.0/14 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on 2.60.0.0/16
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Sep 28, 2018 |
Whois
Registration for this announcement
- Range
- 2.
60. 0. 0/ 16 - Netname
- RU-SIBNET
- Registrant country
- RU
- Organization
- Not stated by the registry
- Type
- LIR-PARTITIONED PA
- Created
- Nov 2, 2010
- Updated
- Jun 27, 2025
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 8, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE