Data as of Nov 22, 2026

188.75.220.0/22

7 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

631 observations

/24s with the most always-on exits

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPFly
  • Infatica
  • Kookey
  • MangoProxy
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • SOTAPROXY
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.75.192.0/18
since Feb 2026
AS8359Mobile551
139 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.220.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.

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