Data as of Nov 15, 2026

83.242.248.0/24

1 residential-proxy exit · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
10
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxyma
  • SPYDERPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.242.248.0/22
since Aug 2006
AS41209Residential2
1 always on
MTS PJSC
83.242.128.0/17
since Apr 2009
AS8359Mobile136
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
Sep 2009
Current origin since
Sep 2009 · 17 yr
Origin networks
1