Data as of Nov 14, 2026

185.8.20.0/22

7 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
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
12
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

11 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.8.20.0/2403
185.8.21.0/2402
185.8.22.0/2402

Proxy providers listing exits

  • 711Proxy
  • DataImpulse
  • EZProxies
  • FloppyData
  • IPCola
  • IPFly
  • IPPeak
  • NovaProxy
  • Proxiware
  • Proxy4U
  • ProxyStyler
  • PuraRoute

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
185.8.20.0/221,024RU-MTU-20121026MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PADec 30, 2025abuse@mtu.ru
└ 185.8.20.0/23512OOOSET-NETOOO SETASSIGNED PAFeb 12, 2013abuse@mtu.ru
via RU-MTU-20121026
└ 185.8.22.0/23512OOOSET-NETOOO SETASSIGNED PAFeb 12, 2013abuse@mtu.ru
via RU-MTU-20121026

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2015
Current origin since
Jul 2015 · 11 yr
Origin networks
1