Data as of Nov 17, 2026

81.201.16.0/20

888 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
75% of it

Residential-proxy exits

Proxy exits
888
22% of its addresses · 30 days
Spread
6 of 16
/24s with at least one exit
Providers
138
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

104K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LITPORT_LIMA
  • LOKIPROXY
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSTPROXY_LITE
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PROXY_CC
  • PYPROXY
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
81.201.30.0/23
since Feb 2024
AS8359Mobile4MTS 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.201.16.0/204,096RU-MTU-20060619MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 19, 2006abuse@mtu.ru
└ 81.201.16.0/221,024MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.20.0/23512MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.22.0/23512MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.24.0/23512MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.26.0/23512MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.28.0/25128MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.28.128/2664MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.28.192/2664MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.29.0/2664MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.29.64/2664MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.29.128/25128MTS-SPB-FIXOJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.30.0/24256MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.31.0/2664MTS-SPB-FIXPJSC "Mobile TeleSystems"ASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.31.64/2664MTS-SPB-FIXCustomer NATASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.31.128/2664MTS-SPB-FIXNOC equipmentASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619
└ 81.201.31.192/2664MTS-SPB-FIXPublic service equipmentASSIGNED PAJul 23, 2014abuse@mtu.ru
via RU-MTU-20060619

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
TypeAddressesShareRanges
Mobile3,07275%4
Residential1,02425%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2006
Current origin since
Sep 2014 · 12 yr
Origin networks
2
Last change of origin
Sep 2014
Recorded history

History

Handoffs
1