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

94.243.6.0/23

7 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS8359
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
1.4% of its addresses · 30 days
Always-on exits
1
14% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.243.6.0/2412
94.243.7.0/2405

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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.6.0/24256PrimorskiyKrai-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.7.0/24256PrimorskiyKrai-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2025
Current origin since
Feb 2025 · 1.8 yr
Origin networks
1