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

94.243.0.0/22

1,024 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
1,024
100% of its addresses · 30 days
Always-on exits
55
5.4% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
87
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

375K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.243.2.0/2418256
94.243.0.0/2414256
94.243.1.0/2412255
94.243.3.0/2411256

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PSBProxy
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy

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.0.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.1.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.2.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.3.0/24256Khabarovsk-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
Nov 2024
Current origin since
Nov 2024 · 2.0 yr
Origin networks
1