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

94.243.20.0/22

4 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS8359
Type
Residential

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
6
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • IPFly
  • NSocks
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
94.243.20.0/24
since Mar 2025
AS49350Residential4MTS PJSC
94.243.21.0/24
since Mar 2025
AS49350ResidentialMTS PJSC
94.243.22.0/24
since Mar 2025
AS49350ResidentialMTS PJSC
94.243.23.0/24
since Mar 2025
AS49350ResidentialMTS 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.20.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.21.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.22.0/24256Khabarovsk-FIXunknownASSIGNED PAOct 16, 2026abuse@mtu.ru
via RU-MTU-20081021
└ 94.243.23.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
Mar 2025
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1