Data as of Nov 14, 2026

81.20.196.0/22

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
84% of it

Residential-proxy exits

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

Exits seen per day

6 observations

Proxy providers listing exits

  • BottingTools
  • IPFly
  • PuraRoute

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.196.0 - 81.20.196.159160INTELECOM-VPNIndustrial Telecom VPNASSIGNED PAAug 30, 2004abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.196.160 - 81.20.196.25596INTELECOM-PPPIndustrial Telecom VPNASSIGNED PAApr 19, 2007abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.197.0/24256INTELECOM-xDSL-links-IPv4-pool-NETp2p and static IP pool for (xEthr, xDSL, Wi-Fi .. )ASSIGNED PAApr 20, 2007abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.198.0/24256INTELECOM-PPP-clients-IPv4-pool198p2p and static IP pool for (xEthr, xDSL, Wi-Fi .. )ASSIGNED PAJun 20, 2014abuse@mtu.ru
via RU-MTU-20020205
└ 81.20.199.0/24256INTELECOM-white-IP-POOL-for-B2CWhite Pool IPv4 address for customersASSIGNED PAJun 23, 2014abuse@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

1,024 addresses
TypeAddressesShareRanges
Residential86484%4
Unknown16016%1

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