Data as of Nov 19, 2026

213.128.9.0/24

7 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
29
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 9Proxy
  • AnyIP
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • RainProxy
  • RealProxy
  • ResiProxies
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.128.0.0/19
since Jun 2008
AS42087Residential133
12 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