Data as of Nov 21, 2026

213.128.8.0/24

4 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
25
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

333 observations

Proxy providers listing exits

  • BlurPath
  • BottingTools
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPRoyal
  • KindProxy
  • Kookey
  • MoMoProxy
  • Novada
  • PrivateByte
  • Proxmint
  • Proxy302
  • Proxy4U
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RapidProxy
  • SwiftProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.128.0.0/19
since Jun 2008
AS42087Residential135
15 always on
MTS PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.128.0.0/198,192RU-MTU-20080526MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAMay 26, 2008abuse@mtu.ru
└ 213.128.0.0/204,096ru-kanal7CJSC Cannel-7ASSIGNED PAMay 26, 2008abuse@mtu.ru
via RU-MTU-20080526

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

213.128.0.0/20

Routing history

Pattern
Stable
First seen
Oct 2017
Current origin since
Oct 2017 · 9.1 yr
Origin networks
1