Data as of Nov 16, 2026

85.235.178.0/23

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

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

Exits seen per day

97 observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • GSocks
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.235.160.0/19
since Apr 2009
AS8359Mobile25
1 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
85.235.160.0/198,192RU-MTU-20050512MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMay 12, 2005abuse@mtu.ru
└ 85.235.178.0/23512b2bhub-moscow-1MTS ipv4 broadband network Moscow (b2b)SUB-ALLOCATED PAFeb 3, 2023abuse@mtu.ru
via RU-MTU-20050512

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