LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

80.71.164.0/24

2 residential-proxy exits · 30 days

MTS PJSC

Announcement
80.71.160.0/19
No RPKI
Announced by
AS21365
Type
Residential
63% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
23
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

609 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.71.160.0/198,192RU-MTU-20010607MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 8, 2004abuse@mtu.ru
└ 80.71.164.16 - 80.71.164.6348PETROV-1Sergey Petrov networkASSIGNED PAJun 7, 2004abuse@mtu.ru
via RU-MTU-20010607
└ 80.71.164.64/2732PRONTO-1Pronto-Novosibirsk networkASSIGNED PAJun 7, 2004abuse@mtu.ru
via RU-MTU-20010607
└ 80.71.164.224/2816Alpha-1Alpha Ltd. networkASSIGNED PAJun 8, 2004abuse@mtu.ru
via RU-MTU-20010607

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

256 addresses
TypeAddressesShareRanges
Residential16063%3
Business9638%3

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 80.71.160.0/19

80.71.160.0/19

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Jul 2010 · 16 yr
Origin networks
2
Last change of origin
Jul 2010
Recorded history

History

Handoffs
1