Data as of Nov 5, 2026
87.225.80.0/21
1 anonymizer address · 0.05% · VPN486 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
486
24% of its addresses · 30 days
Always-on exits
9
1.9% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
83
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
39K observations
- VPN · anonymizer
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 87.225.80.0/24 | 3 | 53 | |
| 87.225.81.0/24 | 2 | 79 | |
| 87.225.83.0/24 | 1 | 67 | |
| 87.225.87.0/24 | 1 | 63 | |
| 87.225.84.0/24 | 1 | 61 | |
| 87.225.85.0/24 | 1 | 47 | |
| 87.225.82.0/24 | 0 | 65 | |
| 87.225.86.0/24 | 0 | 54 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- TrueProxies
- VantageProxies
- VitalData
- VitalExclusive
- VitalProxy
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 87.225.80.0/21 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 10.05% | 1 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
87.225.80.0/21
From the registry to its use
- Mar 15, 2007– Feb 1, 2010
- Mar 15, 2010– today
- Nov 18, 2013Registry recordPJSC RostelecomALLOCATED PA87.224.128.0 - 87.225.127.255
- Dec 8, 2017– today
- Oct 18, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- todayUsedVPN GateVPN
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.225.80.0/20 since Mar 2010 | AS34584 | Residential | 802 21 always on | PJSC Rostelecom | |
| 87.225.64.0/18 since Jul 2006 | AS34584 | Residential | 2,805 124 always on | PJSC Rostelecom | |
| 87.225.0.0/17 since Feb 2007 | AS34584 | Residential | 5,711 146 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. | 65,536 | RU-RTK-20050614 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Nov 18, 2013 | abuse@ |
| └ 87.225.80.0/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-334 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.80.128/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-334 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.80.192/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Leninskoe village, central node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.81.0/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Nikolaevsk-at-Amur town , ATS-27 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.81.128/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Nikolaevsk-at-Amur town , central node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.82.0/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-540 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.82.64/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-540 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.82.128/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-564 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.82.160/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-563 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.82.192/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-5610 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.83.0/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-540 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.83.128/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-530 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.84.0/24 | 256 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-51 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.85.0/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-51 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.85.128/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-21 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.85.192/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Sovetskaya Gavan town, central node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.86.0/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, ATS-293 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.86.128/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-274 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.86.160/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-275 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.86.192/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-2761 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.86.224/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-2762 node | ASSIGNED PA | Dec 29, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87. | 17 | KHT-DTK | For support wireless connections for clients of the DalTeleKom (DTK)- ISP | ASSIGNED PA | Jul 20, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.87.128/29 | 8 | KHT-KHB-TRANSPORT-AGENCY | for terminal stations in first office Khabarovsk Transport Agency | ASSIGNED PA | Aug 2, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.87.136/29 | 8 | KHT-KHB-OPTIMA-FAREAST | for web servers | ASSIGNED PA | Aug 16, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.87.144/29 | 8 | KHT-KHB-BAZALIT | for internet server | ASSIGNED PA | Feb 19, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.87.152/29 | 8 | KHT-KHB-ALFA-BANK | for xDSL modem and router | ASSIGNED PA | Jul 8, 2007 | abuse@ via RU-RTK-20050614 |
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
2,048 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 1,998 | 98% | 4 | |
| Business | 49 | 2.4% | 5 | |
| VPNanonymizer | 1 | 0.05% | 1 |
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
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Mar 2007
- Current origin since
- Dec 2017 · 8.9 yr
- Origin networks
- 2
- Last change of origin
- Dec 2017
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 87.225.80.0/21 | AS12389 | /21 | RIPE | RPKI valid |
| 87.225.80.0/20 | AS34584 | /20 | RIPE | Another network |
| 87.225.64.0/18 | AS34584 | /18 | RIPE | Another network |
| 87.225.0.0/17 | AS34584 | /17 | RIPE | Another network |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 18, 2018 |
Whois
Registration for this announcement
- Range
- 87.
224. 128. 0 - 87. 225. 127. 255 - Netname
- RU-RTK-20050614
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Nov 18, 2013
- Updated
- Jun 5, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jun 23, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE