Data as of Nov 10, 2026

178.72.92.0/23

2 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
2
0.39% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
13
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

28 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.72.92.0/2401
178.72.93.0/2401

Proxy providers listing exits

  • CatProxies
  • EnigmaProxy
  • Evomi
  • FloppyData
  • Geonode
  • HideProxy
  • IPFly
  • InfiniteProxies
  • ProxiesVision
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.72.64.0/18
since Oct 2023
AS8359Mobile2,170
486 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.92.0/23512TNGS-NORTHNETJSC Regional Technical CentreASSIGNED PAJul 1, 2019abuse@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
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1