Data as of Nov 13, 2026

46.20.187.0/24

17 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Providers
40
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.8K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GhostConnect
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyStyler
  • PuraRoute
  • RainProxy
  • StrikeProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.20.176.0/20
since Sep 24, 2026
AS8359Residential169MTS 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
46.20.176.0/204,096RU-MTU-20101005MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 5, 2010abuse@mtu.ru
└ 46.20.184.0/212,048LLC-ZHANR-NETCJSC ZHANR LIR Infrastructure (9-th dynamic PPP pool)SUB-ALLOCATED PAMay 19, 2022abuse@mtu.ru
via RU-MTU-20101005
└ 46.20.187.0/24256b2bhub-vladimir-2unknownSUB-ALLOCATED PAJun 24, 2022abuse@mtu.ru
via LLC-ZHANR-NET

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
Jun 2022
Current origin since
Jun 2022 · 4.4 yr
Origin networks
1