Data as of Nov 17, 2026

83.242.254.0/24

3 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
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
30
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

744 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxio
  • Proxiware
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • StrikeProxy
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.242.252.0/22
since Feb 2021
AS41209Residential12
2 always on
MTS PJSC
83.242.128.0/17
since Apr 2009
AS8359Mobile138
4 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
83.242.128.0/1732,768RU-MTU-20040326MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMar 26, 2004abuse@mtu.ru
└ 83.242.248.0/212,048COMSTAR-VOLGAThe branch of "Comstar-UTS" in Volga regionASSIGNED PAJul 6, 2006abuse@mtu.ru
via RU-MTU-20040326

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