Data as of Nov 4, 2026
89.20.0.0/20
445 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
445
11% of its addresses · 30 days
Always-on exits
28
6.3% of its exits
Spread
16 of 16
/24s with at least one exit
Providers
87
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
55K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 89.20.4.0/24 | 5 | 30 | |
| 89.20.15.0/24 | 3 | 28 | |
| 89.20.9.0/24 | 3 | 21 | |
| 89.20.0.0/24 | 2 | 39 | |
| 89.20.13.0/24 | 2 | 32 | |
| 89.20.7.0/24 | 2 | 30 | |
| 89.20.14.0/24 | 2 | 28 | |
| 89.20.12.0/24 | 2 | 27 | |
| 89.20.2.0/24 | 1 | 35 | |
| 89.20.11.0/24 | 1 | 28 | |
| 89.20.10.0/24 | 1 | 27 | |
| 89.20.5.0/24 | 1 | 27 | |
| 89.20.1.0/24 | 1 | 26 | |
| 89.20.8.0/24 | 1 | 23 | |
| 89.20.6.0/24 | 1 | 19 | |
| 89.20.3.0/24 | 0 | 24 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- 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
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PacketStream
- PrivateByte
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- StrikeProxy
- TalorData
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 89.20.0.0/19 | 8,192 | RU-RTK-20060829 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Aug 29, 2006 | [email protected] |
| └ 89.20.0.0/20 | 4,096 | LENOBL-ADSL-AVANGARD-NET | Address for clients of Avangard-ADSL | ASSIGNED PA | Mar 30, 2016 | [email protected] via RU-RTK-20060829 |
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
Announced by
Covering announcement 89.20.0.0/19
- Prefix
- 89.20.0.0/19
- Announced by
- AS12389 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 444
- Always-on exits
- 28
- RPKI
- RPKI valid
- Netname
- RU-RTK-20060829
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
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 89.20.0.0/19
89.20.0.0/19
Routing history
- Pattern
- Rotating
- First seen
- Sep 2006
- Current origin since
- Apr 2024 · 2.5 yr
- Origin networks
- 3
- Last change of origin
- Nov 2021
Recorded history
History
- Handoffs
- 4
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 89.20.0.0/19 | AS12389 | /19 | RIPE | RPKI valid |
IRR
Route objects on 89.20.0.0/19
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 31, 2018 |
Whois
Registration for this announcement
- Range
- 89.20.0.0/19
- Netname
- RU-RTK-20060829
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Aug 29, 2006
- Updated
- Jun 6, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Aug 29, 2006
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE