Data as of Nov 14, 2026

80.80.199.0/24

2 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

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

520 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GonzoProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.80.192.0/21
since Apr 2020
AS40993Residential1,037
99 always on
MTS PJSC
80.80.192.0/20
since Dec 2008
AS40993Residential1,037
99 always on
MTS PJSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
80.80.192.0/204,096RU-MTU-20081015MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 15, 2008abuse@mtu.ru
└ 80.80.192.0/212,048RU-ALTAIR-20081203-1unknownASSIGNED PADec 3, 2008abuse@mtu.ru
via RU-MTU-20081015

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

80.80.198.0/23

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1