Data as of Nov 6, 2026
87.253.24.0/21
495 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
495
24% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
81
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
24K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 87.253.25.0/24 | 0 | 68 | |
| 87.253.24.0/24 | 0 | 67 | |
| 87.253.26.0/24 | 0 | 65 | |
| 87.253.27.0/24 | 0 | 64 | |
| 87.253.31.0/24 | 0 | 64 | |
| 87.253.29.0/24 | 0 | 61 | |
| 87.253.30.0/24 | 0 | 57 | |
| 87.253.28.0/24 | 0 | 50 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- IPFly
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.253.0.0/19 since Apr 2017 | AS13118 | Residential | 1,925 1 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 87.253.24.0/22 since Oct 2017 | AS12389 | Residential | 264 | PJSC Rostelecom | |
| 87.253.28.0/22 since Oct 2017 | AS12389 | Residential | 232 | 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.253.0.0/19 | 8,192 | RU-RTK-20071212 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Dec 12, 2007 | abuse@ |
| └ 87.253.24.0/22 | 1,024 | MACROREGIONAL_ | OJSC Rostelecom, Yaroslavl Branch | ASSIGNED PA | Apr 10, 2026 | abuse@ via RU-RTK-20071212 |
| └ 87.253.28.0/22 | 1,024 | MACROREGIONAL_ | OJSC Rostelecom, Yaroslavl Branch | ASSIGNED PA | Apr 10, 2026 | abuse@ via RU-RTK-20071212 |
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
AS13118
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Mar 23, 2000
- Domain
- rostelecom.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2008
- Current origin since
- Apr 2008 · 19 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 87.253.24.0/21 | AS13118 | /21 | RIPE | RPKI valid |
| 87.253.0.0/19 | AS13118 | /19 | RIPE | Too specific |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS13118 | RIPE | Yaroslavsky Branch | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 87.
253. 0. 0/ 19 - Netname
- RU-RTK-20071212
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 12, 2007
- Updated
- May 25, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 12, 2007
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE