Data as of Nov 9, 2026
87.251.96.0/19
126 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
126
1.5% of its addresses · 30 days
Always-on exits
15
12% of its exits
Spread
22 of 32
/24s with at least one exit
Providers
81
selling exits here
Oct 10, 2026 – Nov 8, 2026
Exits seen per day
36K observations
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- MangoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYWING_BASIC
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- Proxyma
- PuraRoute
- RainProxy
- ResiProxies
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_PREMIUM
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 87.251.96.0/19 | 8,192 | RU-RTK-20050912 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Sep 12, 2005 | abuse@ |
| └ 87.251.96.0/24 | 256 | SAKHALIN-YS-DIALUP | Rostelecom Dial-Up pool in Y.-Sakhalinsk | ASSIGNED PA | Feb 22, 2013 | abuse@ via RU-RTK-20050912 |
| └ 87.251.97.0/24 | 256 | SAKHALIN-YS-PPPOE-STAT10 | Rostelecom PPPoE pool in Y.-Sakhalinsk | ASSIGNED PA | Feb 22, 2013 | abuse@ via RU-RTK-20050912 |
| └ 87.251.98.0/23 | 512 | SAKHALIN-YS-DSL1 | Dalsvyaz DSL pool in Y.-Sakhalinsk | ASSIGNED PA | Dec 23, 2005 | abuse@ via RU-RTK-20050912 |
| └ 87. | 2,048 | SAKHALIN-YS-DSL2 | Dalsvyaz DSL pool in Y.-Sakhalinsk | ASSIGNED PA | Mar 22, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.108.0/22 | 1,024 | SAKHALIN-YS-DSL8 | Dalsvyaz DSL pool in Y.-Sakhalinsk | ASSIGNED PA | Oct 24, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.113.0/24 | 256 | SAKHALIN-UGL-STATIC-DSL1 | static address for DSL customers in Nevelsk | ASSIGNED PA | Mar 3, 2011 | abuse@ via RU-RTK-20050912 |
| └ 87.251.114.0/24 | 256 | SAKHALIN-SKR-DSL-1 | DSL pool for S-Kurilsk node | ASSIGNED PA | Aug 6, 2007 | abuse@ via RU-RTK-20050912 |
| └ 87.251.115.0/25 | 128 | SAKHALIN-YKR-DSL-1 | DSL pool for Y-Kurilsk node | ASSIGNED PA | Oct 3, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.115.128/25 | 128 | SAKHALIN-KUR-DSL-1 | DSL pool for Kurilsk node | ASSIGNED PA | Oct 3, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.116.0/24 | 256 | SAKHALIN-KRS-DSL-1 | DSL pool for Korsakov node | ASSIGNED PA | Sep 14, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.117.0/24 | 256 | SAKHALIN-TMR-DSL-1 | DSL pool for Tomary node | ASSIGNED PA | Sep 11, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.118.0/24 | 256 | SAKHALIN-ANV-DSL-2 | DSL pool for Aniva node | ASSIGNED PA | Aug 21, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.119.0/24 | 256 | SAKHALIN-ALK-DSL-1 | DSL pool for Aleksandrovsk node | ASSIGNED PA | Aug 13, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.120.0/24 | 256 | SAKHALIN-TMV-DSL-1 | DSL pool for Tymovsk node | ASSIGNED PA | Aug 13, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.121.0/24 | 256 | SAKHALIN-SMR-DSL-1 | DSL pool for Smirnykh node | ASSIGNED PA | Aug 8, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.122.0/24 | 256 | SAKHALIN-MKR-DSL-1 | DSL pool for Makarov node | ASSIGNED PA | Aug 7, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.123.0/24 | 256 | SAKHALIN-KHL-DSL-3 | DSL pool for Kholmsk node | ASSIGNED PA | Jun 25, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.124.0/24 | 256 | SAKHALIN-DLN-DSL-3 | DSL pool for Dolinsk node | ASSIGNED PA | Jun 20, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.125.0/24 | 256 | SAKHALIN-PRN-DSL-2 | DSL pool for Poronajsk node | ASSIGNED PA | May 2, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.126.0/24 | 256 | SAKHALIN-NGL-DSL-1 | DSL pool for Nogliki node | ASSIGNED PA | Mar 21, 2006 | abuse@ via RU-RTK-20050912 |
| └ 87.251.127.0/24 | 256 | SAKHALIN-OKHA-DSL-2 | DSL pool for Okha node | ASSIGNED PA | Feb 8, 2006 | abuse@ via RU-RTK-20050912 |
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
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
Who has announced this prefix
Summary
Routing history
- Pattern
- Rotating
- First seen
- Jan 2006
- Current origin since
- Nov 2023 · 3.0 yr
- Origin networks
- 2
- Last change of origin
- Nov 2023
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 87.
251. 96. 0/ 19 - Netname
- RU-RTK-20050912
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Sep 12, 2005
- Updated
- Jun 23, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Sep 12, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE