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

88.80.59.0/24

5 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS39001
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
29
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.80.32.0/19
since Dec 2005
AS39001Residential1,027
61 always on
MTS PJSC

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
88.80.32.0/198,192RU-MTU-20051124MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 24, 2005abuse@mtu.ru
└ 88.80.54.0 - 88.80.61.2552,048TVIN-NETJSC "Cable tv Mark"ASSIGNED PADec 6, 2006abuse@mtu.ru
via RU-MTU-20051124

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

AnnouncementRouting historyWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2026
Current origin since
Jan 2026 · 10 mo
Origin networks
1