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

178.72.64.0/22

11 residential-proxy exits · 30 days

MTS PJSC

Announcement
178.72.64.0/18
No RPKI
Announced by
AS8359
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Always-on exits
1
9.1% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
36
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.72.67.0/24110
178.72.66.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each 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.64.0/221,024TNGS-SOUTHNETTyumen branch of JSC "MTS"ASSIGNED PAMay 29, 2015abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 178.72.64.0/18

178.72.64.0/18

Routing history

Pattern
Stable
First seen
Oct 2023
Current origin since
Oct 2023 · 3.0 yr
Origin networks
1