Data as of Nov 8, 2026
87.103.128.0/17
5 anonymizer addresses · 0.02% · VPN600 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
600
1.8% of its addresses · 30 days
Always-on exits
86
14% of its exits
Spread
49 of 128
/24s with at least one exit
Providers
113
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
179K observations
- VPN · anonymizer
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 87.103.193.0/24 | 7 | 28 | |
| 87.103.201.0/24 | 6 | 23 | |
| 87.103.194.0/24 | 6 | 21 | |
| 87.103.198.0/24 | 5 | 25 | |
| 87.103.197.0/24 | 5 | 17 | |
| 87.103.196.0/24 | 5 | 17 | |
| 87.103.172.0/24 | 4 | 21 | |
| 87.103.192.0/24 | 4 | 20 | |
| 87.103.173.0/24 | 4 | 19 | |
| 87.103.245.0/24 | 4 | 12 | |
| 87.103.202.0/24 | 3 | 18 | |
| 87.103.204.0/24 | 3 | 13 | |
| 87.103.242.0/24 | 3 | 13 | |
| 87.103.203.0/24 | 2 | 14 | |
| 87.103.224.0/24 | 2 | 14 | |
| 87.103.200.0/24 | 2 | 12 | |
| 87.103.208.0/24 | 2 | 12 | |
| 87.103.135.0/24 | 2 | 11 | |
| 87.103.252.0/24 | 2 | 7 | |
| 87.103.199.0/24 | 1 | 20 | |
| 87.103.175.0/24 | 1 | 18 | |
| 87.103.240.0/24 | 1 | 17 | |
| 87.103.234.0/24 | 1 | 17 | |
| 87.103.133.0/24 | 1 | 16 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 87.103.128.0/17 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 50.02% | 4 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
87.103.128.0/17
From the registry to its use
- Oct 20, 2005Registry recordPJSC RostelecomALLOCATED PA87.103.128.0/17
- Dec 4, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.216.0/21
- Dec 4, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.216.0/22
- Dec 4, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.220.0/22
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.216.0/23
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.216.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.217.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.218.0/23
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.218.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.219.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.220.0/23
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.220.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.221.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.222.0/23
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.222.0/24
- Dec 6, 2006Route objectAS16287 PJSC RostelecomRIPE route object for AS16287 PJSC Rostelecom, maintainer RU-KUZBASSNET-MNT87.103.223.0/24
- Oct 28, 2018– today
- Nov 1, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- todayUsedVPN GateVPN
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Anonymizer addresses | Operator | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|---|
| 87.103.128.0/21 since Jul 2015 | AS12389 | Residential | 48 4 always on | PJSC Rostelecom via Allocation for Irkutsk regional branche of the JSC Sibirtelecom. | |||
| 87.103.144.0/20 since Mar 2016 | AS12389 | Residential | PJSC Rostelecom via Allocation for Krasnoyarsk regional branche of the JSC Sibirtelecom. | ||||
| 87.103.168.0/22 since Jan 2015 | AS12389 | Residential | 19 1 always on | PJSC Rostelecom | |||
| 87.103.172.0/22 since Jul 2015 | AS12389 | Residential | 72 9 always on | PJSC Rostelecom | |||
| 87.103.176.0/20 since Dec 2022 | AS12389 | Residential | PJSC Rostelecom via Allocation for Omsk regional branch of the JSC Sibirtelecom. | ||||
| 87.103.192.0/22 since Nov 2015 | AS12389 | Residential | 10.10%VPN | VPN servicesoperated by VPN Gate | 81 17 always on | PJSC Rostelecom | |
| 87.103.196.0/22 since Feb 2016 | AS12389 | Residential | 79 16 always on | PJSC Rostelecom | |||
| 87.103.200.0/22 since Nov 2015 | AS12389 | Residential | 20.20%VPN | VPN servicesoperated by VPN Gate | 67 13 always on | PJSC Rostelecom | |
| 87.103.204.0/22 since Nov 2016 | AS12389 | Residential | 33 3 always on | PJSC Rostelecom | |||
| 87.103.208.0/21 since Nov 2015 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 61 7 always on | PJSC Rostelecom | |
| 87.103.224.0/21 since Jun 2023 | AS12389 | Residential | 14 2 always on | PJSC Rostelecom | |||
| 87.103.232.0/21 since Jul 2015 | AS12389 | Residential | 19 1 always on | PJSC Rostelecom | |||
| 87.103.234.0/24 since Jul 2015 | AS39407 | Residential | 17 1 always on | PJSC Rostelecom | |||
| 87.103.240.0/20 since Aug 2016 | AS12389 | Residential | 10.02%VPN | VPN servicesoperated by VPN Gate | 107 13 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 87.103.128.0/17 | 32,768 | RU-RTK-20051020 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Oct 20, 2005 | abuse@ |
| └ 87.103.128.0/20 | 4,096 | RU-SIBNET-IRKUTSK | Allocation for Irkutsk regional branche of the JSC Sibirtelecom. | LIR-PARTITIONED PA | Oct 25, 2005 | abuse@ via RU-RTK-20051020 |
| └ 87.103.128.0/23 | 512 | IRTEL | Irkutsk Central Telegraph | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87.103.130.0/23 | 512 | IRTELDIALUP-NET | Irkutsk Central Telegraph | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87.103.132.0/25 | 128 | SIBNET-IPTV | IPTV platform | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87.103.132.128/25 | 128 | IRTEL | Irkutsk Central Telegraph | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87. | 768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87.103.136.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 12, 2010 | abuse@ via RU-SIBNET-IRKUTSK |
| └ 87.103.144.0/20 | 4,096 | RU-SIBNET-KRASNOYARSK | Allocation for Krasnoyarsk regional branche of the JSC Sibirtelecom. | LIR-PARTITIONED PA | Oct 27, 2005 | abuse@ via RU-RTK-20051020 |
| └ 87.103.144.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 4, 2007 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87.103.152.48/28 | 16 | KRASNET-OSB0279NET | SberBank N0279 | ASSIGNED PA | Mar 29, 2006 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87.103.152.104/30 | 4 | Motion-VoIP | Motion Limited | ASSIGNED PA | Aug 17, 2006 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87.103.152.108/30 | 4 | Motion-VoIP | Motion Limited | ASSIGNED PA | Aug 17, 2006 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87. | 512 | ATOMLINKNET | Public network for Science Technical Center | ASSIGNED PA | May 30, 2008 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87. | 1,280 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 4, 2007 | abuse@ via RU-SIBNET-KRASNOYARSK |
| └ 87.103.160.0/21 | 2,048 | STBUR-NET | (IR000879) The Buryat branch of JSC "Sibirtelecom" | ASSIGNED PA | Nov 1, 2005 | abuse@ via RU-RTK-20051020 |
| └ 87.103.168.0/22 | 1,024 | GAGUES | For Gorniy Altay regional branch of the JSC Sibirtelecom. | ASSIGNED PA | Nov 14, 2005 | abuse@ via RU-RTK-20051020 |
| └ 87.103.172.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | May 4, 2006 | abuse@ via RU-RTK-20051020 |
| └ 87.103.176.0/20 | 4,096 | RU-SIBNET-OMSK | Allocation for Omsk regional branch of the JSC Sibirtelecom. | LIR-PARTITIONED PA | Nov 8, 2005 | abuse@ via RU-RTK-20051020 |
| └ 87. | 768 | OTTS-DIALUP | Omsk Telegraph Telephone Station | ASSIGNED PA | Mar 20, 2006 | abuse@ via RU-SIBNET-OMSK |
| └ 87. | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 10, 2025 | abuse@ via RU-SIBNET-OMSK |
| └ 87. | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 10, 2025 | abuse@ via RU-SIBNET-OMSK |
| └ 87.103.191.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 10, 2025 | abuse@ via RU-SIBNET-OMSK |
| └ 87.103.192.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Dec 8, 2008 | abuse@ via RU-RTK-20051020 |
| └ 87.103.192.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 8, 2008 | abuse@ via RU-SIBNET |
| └ 87.103.200.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 8, 2008 | abuse@ via RU-SIBNET |
| └ 87.103.201.0/25 | 128 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 23, 2008 | abuse@ via RU-SIBNET |
| └ 87.103.201.128/25 | 128 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 23, 2008 | abuse@ via RU-SIBNET |
| └ 87.103.202.0/23 | 512 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2010 | abuse@ via RU-SIBNET |
| └ 87.103.204.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 14, 2011 | abuse@ via RU-SIBNET |
| └ 87.103.208.0/20 | 4,096 | WEBSTREAM | OJSC "Rostelecom" | ASSIGNED PA | Nov 2, 2007 | abuse@ via RU-SIBNET |
| └ 87.103.224.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 10, 2025 | abuse@ via RU-RTK-20051020 |
| └ 87.103.232.0/23 | 512 | CHITA-NETS | CJSC ChitaNet | ASSIGNED PA | May 18, 2009 | abuse@ via RU-RTK-20051020 |
| └ 87.103.234.0/23 | 512 | CHITATELECOM-NETWORKS-ADDOPERATORS | access net clients | ASSIGNED PA | May 18, 2009 | abuse@ via RU-RTK-20051020 |
| └ 87.103.236.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jul 10, 2025 | abuse@ via RU-RTK-20051020 |
| └ 87.103.240.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 22, 2005 | abuse@ via RU-RTK-20051020 |
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
32,768 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 32,227 | 98% | 27 | |
| Business | 536 | 1.6% | 7 | |
| VPNanonymizer | 5 | 0.02% | 5 |
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
- Stable
- First seen
- Oct 2018
- Current origin since
- Oct 2018 · 8.0 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 87.103.128.0/17 | AS12389 | /21 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Jun 27, 2025 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 87.103.216.0/21 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 4, 2006 |
| 87.103.216.0/22 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 4, 2006 |
| 87.103.216.0/23 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.216.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.217.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.218.0/23 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.218.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.219.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.220.0/22 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 4, 2006 |
| 87.103.220.0/23 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.220.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.221.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.222.0/23 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.222.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
| 87.103.223.0/24 | AS16287 | RIPE | Kuzbass Network | RU-KUZBASSNET-MNT | Dec 6, 2006 |
Whois
Registration for this announcement
- Range
- 87.
103. 128. 0/ 17 - Netname
- RU-RTK-20051020
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Oct 20, 2005
- Updated
- Jun 6, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 20, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE