Data as of Nov 14, 2026

83.242.248.0/22

2 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

125 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.242.248.0/2401
83.242.249.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • IPFly
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxyma
  • PuraRoute
  • SPYDERPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.242.128.0/17
since Apr 2009
AS8359Mobile138
3 always on
MTS PJSC
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
83.242.248.0/24
since Sep 2009
AS41209Residential1MTS PJSC
83.242.249.0/24
since Oct 2007
AS41209Residential1MTS PJSC
83.242.250.0/24
since Dec 2010
AS41209ResidentialMTS PJSC
83.242.251.0/24
since Dec 2010
AS41209ResidentialMTS 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
Aug 2006
Current origin since
Aug 2006 · 20 yr
Origin networks
1