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

178.72.112.0/24

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
178.72.112.0/20
No RPKI
Announced by
AS48541
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
29
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

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

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 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.112.0/212,048NVKZ-MTS-NETMobile TeleSystems Kuzbass branchASSIGNED PASep 29, 2014abuse@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

Covering aggregate above, the prefix's own history below

178.72.112.0/20

Routing history

Pattern
Stable
First seen
Oct 2014
Current origin since
Oct 2014 · 12 yr
Origin networks
1