Data as of Nov 15, 2026

94.72.57.0/24

3 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
35
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

881 observations

Proxy providers listing exits

  • 9Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.72.0.0/18
since May 2013
AS8359Mobile76
1 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
94.72.0.0/1816,384RU-MTU-20080624MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 24, 2008abuse@mtu.ru
└ 94.72.57.0/24256MTS-SPB-HOME-P8MTS SpbASSIGNED PADec 5, 2011abuse@mtu.ru
via RU-MTU-20080624

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

94.72.56.0/22

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1