Data as of Nov 5, 2026
87.225.20.0/22
225 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
225
22% of its addresses · 30 days
Always-on exits
1
0.44% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
63
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
13K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 87.225.20.0/24 | 1 | 49 | |
| 87.225.23.0/24 | 0 | 70 | |
| 87.225.21.0/24 | 0 | 62 | |
| 87.225.22.0/24 | 0 | 44 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- NSocks
- NextProxy
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- PacketStream
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- Shifter
- Smartproxy
- TrueProxies
- VantageProxies
- VitalExclusive
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.225.0.0/18 since Apr 2006 | AS34584 | Residential | 2,906 22 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.20.0/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-37 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.20.32/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Komsomolsk-at-Amur town , ATS-37 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.20.192/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-1 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.20.208/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-1 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.20.224/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-1 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.0/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-2 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.16/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-2 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.32/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-2 node | ASSIGNED PA | Jan 9, 2008 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.64/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-11 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.96/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-3 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.128/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-4 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.160/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-4 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.176/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-11 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.192/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-5 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.224/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-5 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.21.240/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-5 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.0/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-6 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.32/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-6 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.48/28 | 16 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-12 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.64/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-12 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.96/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-7 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.128/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-25 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.160/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-8 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.192/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-9 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.22.224/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-9 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.23.0/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-10 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.23.32/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, HONET-10 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.23.64/26 | 64 | KHT-XDSL | static and PPPoE xDSL links in Beriozovivillage, central node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.23.128/25 | 128 | KHT-XDSL | static and PPPoE xDSL links in Beriozovivillage, central node | ASSIGNED PA | Dec 28, 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.
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
- Jun 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.20.0/22 | AS12389 | /22 | RIPE | RPKI valid |
| 87.225.0.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