Data as of Nov 14, 2026

81.95.16.0/20

8 residential-proxy exits · 30 days

MT-Telecom LLC

Announcement
this exact prefix
No RPKI
Announced by
Type
Unknown
>99% of it

Residential-proxy exits

Proxy exits
8
0.20% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
6 of 16
/24s with at least one exit
Providers
21
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • BestProxy
  • CROXY
  • DataImpulse
  • EnigmaProxy
  • GeekProxy
  • IPFly
  • NSocks
  • NovaProxy
  • Novada
  • PSBProxy
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • ZENPROXY_PREMIUM

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.95.16.0/204,096RU-MT-20060519MT-Telecom LLC (ORG-ML50-RIPE) · RUALLOCATED PAMay 19, 2006hostmaster@mttelecom.ru
└ 81.95.16.0/2732MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAMay 19, 2006hostmaster@mttelecom.ru
└ 81.95.16.48/2816MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAMay 19, 2006hostmaster@mttelecom.ru
└ 81.95.17.48/2816MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAMay 19, 2006hostmaster@mttelecom.ru
└ 81.95.18.0/24256MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAJul 14, 2006hostmaster@mttelecom.ru
└ 81.95.19.0/24256MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAJul 14, 2006hostmaster@mttelecom.ru
└ 81.95.20.0/24256MTTELECOM-NETWORKMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAJul 14, 2006hostmaster@mttelecom.ru
└ 81.95.21.16/2816RENCAP-LANMT-Telecom LLC (ORG-ML50-RIPE) · RUASSIGNED PAJul 18, 2006hostmaster@mttelecom.ru
└ 81.95.23.0/24256MTTELECOM-NETWORKMT-Telecom Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.24.0/24256MTTELECOM-NETWORKMT-Telecom Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.25.0/24256MTTELECOM-NETWORKMT-Telecom Avenu Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.26.0/24256MTTELECOM-NETWORKMT-Telecom Gulliver2 Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.28.0/24256MTTELECOM-NETWORKMT-Telecom Gulliver2 Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.29.0/24256MTTELECOM-NETWORKMT-Telecom Sedova11 Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519
└ 81.95.30.0/23512MTTELECOM-NETWORKMT-Telecom Chapigina Clients NetworkASSIGNED PAApr 22, 2015hostmaster@mttelecom.ru
via RU-MT-20060519

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
Unknown4,080>99%2
Business160.39%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
May 2006
Current origin since
May 2006 · 20 yr
Origin networks
2
Last change of origin
Jul 2026
Recorded history

History

Handoffs
1