Data as of Nov 7, 2026
81.20.192.0/20
10 residential-proxy exits · 30 daysMTS PJSC
Residential-proxy exits
Proxy exits
10
0.24% of its addresses · 30 days
Always-on exits
4
40% of its exits
Spread
5 of 16
/24s with at least one exit
Providers
49
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
8.4K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 81.20.205.0/24 | 4 | 6 | |
| 81.20.195.0/24 | 0 | 1 | |
| 81.20.198.0/24 | 0 | 1 | |
| 81.20.201.0/24 | 0 | 1 | |
| 81.20.203.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FloppyData
- GSocks
- Geonode
- GhostConnect
- GonzoProxy
- HideProxy
- IPFly
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- LemonBright
- LightningProxies
- LudaxProxy
- MangoProxy
- NodeMaven
- NodeProxy
- NovaProxy
- ProxiesVision
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyRack
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- Shifter
- Thordata
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 81.20.194.0/24 since Jun 2013 | AS60833 | Business | MTS PJSC | ||
| 81.20.205.0/24 since Feb 2024 | AS200982 | Residential | 6 4 always on | MTS PJSC |
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 |
|---|---|---|---|---|---|---|
| 81.20.192.0/20 | 4,096 | RU-MTU-20020205 | MTS PJSC (ORG-ZM1-RIPE) · RU | ALLOCATED PA | Dec 23, 2025 | abuse@ |
| └ 81.20.192.0/24 | 256 | INTELECOM-2-NET | Industrial Telecom Inc., Moscow | ASSIGNED PA | Feb 8, 2002 | abuse@ via RU-MTU-20020205 |
| └ 81.20.193.0/24 | 256 | INTELECOM-1-DIALUP | Industrial Telecom Dial-up | ASSIGNED PA | May 18, 2004 | abuse@ via RU-MTU-20020205 |
| └ 81.20.194.0/24 | 256 | NLMK-NET | JSC "NLMK" network | ASSIGNED PA | Feb 27, 2002 | abuse@ via RU-MTU-20020205 |
| └ 81.20.195.0/27 | 32 | STINOL-PLANT-NET | Refrigerator Plant STINOL | ASSIGNED PA | Feb 26, 2002 | abuse@ via RU-MTU-20020205 |
| └ 81. | 33 | INTELECOM-1-COL | Industrial Telecom Colocation | ASSIGNED PA | Sep 2, 2016 | abuse@ via RU-MTU-20020205 |
| └ 81. | 191 | INTELECOM-PPP | Industrial Telecom VPN | ASSIGNED PA | Apr 19, 2007 | abuse@ via RU-MTU-20020205 |
| └ 81. | 160 | INTELECOM-VPN | Industrial Telecom VPN | ASSIGNED PA | Aug 30, 2004 | abuse@ via RU-MTU-20020205 |
| └ 81. | 96 | INTELECOM-PPP | Industrial Telecom VPN | ASSIGNED PA | Apr 19, 2007 | abuse@ via RU-MTU-20020205 |
| └ 81.20.197.0/24 | 256 | INTELECOM-xDSL-links-IPv4-pool-NET | p2p and static IP pool for (xEthr, xDSL, Wi-Fi .. ) | ASSIGNED PA | Apr 20, 2007 | abuse@ via RU-MTU-20020205 |
| └ 81.20.198.0/24 | 256 | INTELECOM-PPP-clients-IPv4-pool198 | p2p and static IP pool for (xEthr, xDSL, Wi-Fi .. ) | ASSIGNED PA | Jun 20, 2014 | abuse@ via RU-MTU-20020205 |
| └ 81.20.199.0/24 | 256 | INTELECOM-white-IP-POOL-for-B2C | White Pool IPv4 address for customers | ASSIGNED PA | Jun 23, 2014 | abuse@ via RU-MTU-20020205 |
| └ 81.20.200.0/23 | 512 | INTELECOM-PPP | Industrial Telecom VPN | ASSIGNED PA | Apr 19, 2007 | abuse@ via RU-MTU-20020205 |
| └ 81. | 152 | INTELECOM-Net-B2B | unknown | ASSIGNED PA | Aug 30, 2016 | abuse@ via RU-MTU-20020205 |
| └ 81.20.202.152/29 | 8 | Betterman-net | Network for Betterman | ASSIGNED PA | Feb 24, 2015 | abuse@ via RU-MTU-20020205 |
| └ 81.20.202.160/28 | 16 | Sez-net | network for OEZ in Lipetsk | ASSIGNED PA | Jun 25, 2014 | abuse@ via RU-MTU-20020205 |
| └ 81. | 80 | INTELECOM-B2B-NET2 | unknown | ASSIGNED PA | Aug 30, 2016 | abuse@ via RU-MTU-20020205 |
| └ 81.20.203.0/24 | 256 | INTELECOM-WHITE-IP-POOL-FOR-B2B | p2p and static IP pool for (xEthr, xDSL, Wi-Fi .. ) | ASSIGNED PA | Nov 21, 2014 | abuse@ via RU-MTU-20020205 |
| └ 81.20.204.0/24 | 256 | INTELECOM-POOL-FOR-B2B-204 | INTELECOM-POOL-FOR-B2B (eth) | ASSIGNED PA | Nov 26, 2014 | abuse@ via RU-MTU-20020205 |
| └ 81.20.205.0/24 | 256 | NET-FOR-TOMSK | unknown | ASSIGNED PA | Feb 21, 2024 | abuse@ via RU-MTU-20020205 |
| └ 81.20.206.0/24 | 256 | INTELECOM-FREE-POOL1 | unknown | ASSIGNED PA | Feb 22, 2024 | abuse@ via RU-MTU-20020205 |
| └ 81.20.207.0/24 | 256 | INTELECOM-FREE-POOL2 | unknown | ASSIGNED PA | Feb 22, 2024 | abuse@ via RU-MTU-20020205 |
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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 2,335 | 57% | 9 | |
| Unknown | 1,017 | 25% | 5 | |
| Business | 744 | 18% | 4 |
Network & registry
Origin network
AS20866
RU
- Name
- MTS PJSC
- Registered
- Feb 7, 2002
- Domain
- mts.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- Jul 2017 · 9.3 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS20866 | RIPE | RU-INTELECOM-NET | INTELECOM-MNT | Feb 12, 2002 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 81.20.192.0/23 | AS20866 | RIPE | RU-INTELECOM-NET | INTELECOM-MNT | May 13, 2013 |
| 81.20.192.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.193.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.195.0/24 | AS20866 | RIPE | RU-INTELECOM-NET-195 | INTELECOM-MNT | May 13, 2013 |
| 81.20.196.0/22 | AS20866 | RIPE | RU-INTELECOM-NET-196 | INTELECOM-MNT | May 13, 2013 |
| 81.20.196.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.197.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.198.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.199.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.200.0/21 | AS20866 | RIPE | RU-INTELECOM-NET-200 | INTELECOM-MNT | May 13, 2013 |
| 81.20.200.0/22 | AS20866 | RIPE | RU-INTELECOM-NET-200-203 | INTELECOM-MNT | May 23, 2014 |
| 81.20.200.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.201.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.202.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.203.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 | |
| 81.20.204.0/22 | AS20866 | RIPE | RU-INTELECOM-NET-204 | INTELECOM-MNT | May 23, 2014 |
| 81.20.204.0/24 | AS20866 | RIPE | INTELECOM-MNT | Sep 29, 2022 |
Whois
Registration for this announcement
- Range
- 81.
20. 192. 0/ 20 - Netname
- RU-MTU-20020205
- Registrant
- MTS PJSC
- Registrant country
- RU
- Organization
- MTS PJSC (ORG-ZM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 23, 2025
- Updated
- Dec 23, 2025
- Maintainer
- MTU-NOC
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 5, 2002
- Status
- assigned
Report abuse
Abuse contact
- abuse@
mtu. ru - Name
- MTU Abuse-c Bender
- Handle
- MAB8359-RIPE