Data as of Nov 11, 2026

178.72.100.0/22

5 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

607 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.72.102.0/2412
178.72.101.0/2403

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • IPFly
  • IPPeak
  • LudaxProxy
  • Oxylabs
  • Proxies.fo
  • Proxio
  • ProxyRack
  • PuraRoute
  • RainProxy
  • StrikeProxy
  • ThunderProxy
  • VibeProxies
  • VitalData

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.72.64.0/18
since Oct 2023
AS8359Mobile2,165
474 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
178.72.64.0/1816,384RU-MTU-20100219MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAFeb 19, 2010abuse@mtu.ru
└ 178.72.100.0/221,024TNGS-NORTHNETJSC Regional Technical CentreASSIGNED PAMay 2, 2017abuse@mtu.ru
via RU-MTU-20100219

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
Nov 2010
Current origin since
Nov 2010 · 16 yr
Origin networks
1