Data as of Nov 16, 2026

91.143.58.0/23

2 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
2
0.39% of its addresses · 30 days
Always-on exits
1
50% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
91.143.59.0/2411
91.143.58.0/2401

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • IPRoyal
  • Kookey
  • NSocks
  • Oxylabs
  • PROXYFALL
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Thordata
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.143.56.0/22
since Dec 2007
AS41822Residential6
1 always on
MTS PJSC
91.143.48.0/20
since Oct 2023
AS8359Mobile25
3 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
91.143.48.0/204,096RU-MTU-20061030MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 30, 2006abuse@mtu.ru
└ 91.143.58.0/23512MTS-NORTHNETPJSC "MTS" branch UralASSIGNED PADec 11, 2015abuse@mtu.ru
via RU-MTU-20061030

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 2009
Current origin since
Aug 2009 · 17 yr
Origin networks
1