Data as of Nov 16, 2026

94.243.16.0/23

6 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
6
1.2% of its addresses · 30 days
Always-on exits
2
33% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
30
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.243.16.0/2424
94.243.17.0/2402

Proxy providers listing exits

  • 9Proxy
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RealProxy
  • ResiProxies
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.243.16.0/22
since Jan 2025
AS8359Residential7
2 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
94.243.0.0/1816,384RU-MTU-20081021MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 21, 2008abuse@mtu.ru
└ 94.243.16.0/24256Tumen-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.17.0/24256Tumen-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021

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
Jan 2025
Current origin since
Jan 2025 · 1.8 yr
Origin networks
1