Data as of Nov 18, 2026

188.75.252.0/22

7 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
75% of it

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
35
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

385 observations
  • Residential
  • Internet provider

/24s with the most always-on exits

/24Always-on exitsProxy exits
188.75.253.0/2404
188.75.255.0/2402
188.75.254.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • Decodo
  • EnigmaProxy
  • Evomi
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HPROXY
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYON
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.75.192.0/18
since Feb 2026
AS8359Mobile553
136 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
188.75.192.0/1816,384RU-MTU-20090825MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAAug 25, 2009abuse@mtu.ru
└ 188.75.252.0/221,024B2B-FIX-SHPD-202601MTS Zabaykal'skiy kraiASSIGNED PAJan 16, 2026abuse@mtu.ru
via RU-MTU-20090825

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
Residential76875%3
Internet provider25625%1

Network & registry

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