LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

46.20.185.0/24

15 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
37
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • CatProxies
  • DataImpulse
  • EZProxies
  • FastProxy
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • KindProxy
  • LUMIPROXY
  • LudaxProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • Novada
  • PROXYSCRAPE
  • Proxmint
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • TrueProxies
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.20.176.0/20
since Sep 24, 2026
AS8359Residential172MTS 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

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Sep 2023
Current origin since
Sep 2023 · 3.1 yr
Origin networks
1