Data as of Nov 20, 2026

81.20.200.0/21

7 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
50% of it

Residential-proxy exits

Proxy exits
7
0.34% of its addresses · 30 days
Always-on exits
4
57% of its exits
Spread
3 of 8
/24s with at least one exit
Providers
54
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.20.205.0/2445
81.20.201.0/2401
81.20.203.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • Geonode
  • GonzoProxy
  • HASDATA
  • IPFly
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.20.205.0/24
since Feb 2024
AS200982Residential5
4 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.20.192.0/204,096RU-MTU-20020205MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 23, 2025abuse@mtu.ru
└ 81.20.200.0/23512INTELECOM-PPPIndustrial Telecom VPNASSIGNED PAApr 19, 2007abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.202.0 - 81.20.202.151152INTELECOM-Net-B2BunknownASSIGNED PAAug 30, 2016abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.202.152/298Betterman-netNetwork for BettermanASSIGNED PAFeb 24, 2015abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.202.160/2816Sez-netnetwork for OEZ in LipetskASSIGNED PAJun 25, 2014abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.202.176 - 81.20.202.25580INTELECOM-B2B-NET2unknownASSIGNED PAAug 30, 2016abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.203.0/24256INTELECOM-WHITE-IP-POOL-FOR-B2Bp2p and static IP pool for (xEthr, xDSL, Wi-Fi .. )ASSIGNED PANov 21, 2014abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.204.0/24256INTELECOM-POOL-FOR-B2B-204INTELECOM-POOL-FOR-B2B (eth)ASSIGNED PANov 26, 2014abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.205.0/24256NET-FOR-TOMSKunknownASSIGNED PAFeb 21, 2024abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.206.0/24256INTELECOM-FREE-POOL1unknownASSIGNED PAFeb 22, 2024abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.207.0/24256INTELECOM-FREE-POOL2unknownASSIGNED PAFeb 22, 2024abuse@mtu.ru
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

2,048 addresses
TypeAddressesShareRanges
Residential1,02450%3
Unknown53626%2
Business48824%3

Network & registry

Routing timeline

Who has announced 81.20.192.0/20

81.20.192.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jul 2017 · 9.3 yr
Origin networks
1