Data as of Nov 5, 2026
87.225.56.0/22
244 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
244
24% of its addresses · 30 days
Always-on exits
2
0.82% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
65
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
16K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 87.225.57.0/24 | 1 | 62 | |
| 87.225.58.0/24 | 1 | 60 | |
| 87.225.59.0/24 | 0 | 63 | |
| 87.225.56.0/24 | 0 | 61 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPPeak
- Infatica
- InfiniteProxies
- LemonLabs
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Proxyma
- PuraRoute
- RainProxy
- Shifter
- Smartproxy
- TrueProxies
- VantageProxies
- VitalData
- 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.56.32/29 | 8 | KHT-KHB-MISHCHERJAKOVA | For terminals | ASSIGNED PA | May 21, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.40/29 | 8 | KHT-KHB-MISHCHERJAKOVA | For terminals | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.64/29 | 8 | KHT-AUSS-Ltd | for terminal stations AUSS Ltd | ASSIGNED PA | Jun 16, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.96/28 | 16 | KHT-KHB-FEDERAL-SECURITY-SERVICE | For servers and terminals | ASSIGNED PA | May 21, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.128/29 | 8 | KHT-SVG-SAVINGS-BANK | for terminals | ASSIGNED PA | Oct 30, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.136/29 | 8 | KHT-KHB-SPECTRUM-AVIA-SERVICE | for terminals | ASSIGNED PA | Oct 30, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.144/28 | 16 | KHT-SVG-ALFA | for remote administration | ASSIGNED PA | Oct 30, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.160/27 | 32 | KHT-XDSL | static and PPPoE xDSL links in Nikolaevsk-at-Amur town , ATS-41 node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.200/29 | 8 | KHT-KHB-LEBEDA | for access to corporate workstation from Internet | ASSIGNED PA | Oct 16, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.216/29 | 8 | KHT-KHB-PACIFIC-MEDIA | for access to corporate workstation from Internet | ASSIGNED PA | Dec 11, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.224/28 | 16 | KHT-KHB-UFSB | for servers | ASSIGNED PA | Dec 11, 2006 | abuse@ via RU-RTK-20050614 |
| └ 87.225.56.240/28 | 16 | KHT-KHB-VOSTOK-AVTOMATIKA | for internet computers | ASSIGNED PA | Feb 21, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.57.0/24 | 256 | KHT-XDSL | static and PPPoE xDSL links in Chegdomyn town, central node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.58.0/24 | 256 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, central node | ASSIGNED PA | Dec 28, 2007 | abuse@ via RU-RTK-20050614 |
| └ 87.225.59.0/24 | 256 | KHT-XDSL | static and PPPoE xDSL links in Khabarovsk city, 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.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
1,024 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 904 | 88% | 7 | |
| Business | 120 | 12% | 11 |
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 2020
- Current origin since
- Jun 2020 · 6.4 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 87.225.56.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-MNT | Mar 11, 2024 |
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