Data as of Nov 16, 2026

81.201.240.0/20

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
98% of it

Residential-proxy exits

Proxy exits
4
0.10% of its addresses · 30 days
Spread
3 of 16
/24s with at least one exit
Providers
10
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

35 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.201.246.0/2402
81.201.244.0/2401
81.201.249.0/2401

Proxy providers listing exits

  • BottingTools
  • EnigmaProxy
  • FLEETPROXY
  • IPFly
  • NovaProxy
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies

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.240.0/204,096RU-MTU-20060623MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 23, 2006abuse@mtu.ru
└ 81.201.240.0/25128MTS-BRNmpls core infrasructureASSIGNED PASep 5, 2017abuse@mtu.ru
via RU-MTU-20060623
└ 81.201.240.192/2664PINA-FORS-RFORS-Region Collocation networkASSIGNED PASep 17, 2007abuse@mtu.ru
via RU-MTU-20060623

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
Residential4,03298%2
Business641.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2006
Current origin since
Jul 2006 · 20 yr
Origin networks
1