Data as of Nov 13, 2026

46.53.128.0/24

5 residential-proxy exits · 30 days

Unitary enterprise A1

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
37
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

723 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.53.128.0/21
since Mar 2020
AS42772Mobile523
107 always on
Unitary enterprise A1

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.53.128.0/1732,768BY-MDC-20100824Unitary enterprise A1 (ORG-JMDC1-RIPE) · BYALLOCATED PAAug 24, 2010abuse@a1.by
└ 46.53.128.0/24256A1-BELARUSUnitary enterprise A1 (ORG-JMDC1-RIPE) · BYASSIGNED PAAug 24, 2010abuse@a1.by

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Sep 2010
Current origin since
Mar 2020 · 6.7 yr
Origin networks
2
Last change of origin
Mar 2020
Recorded history

History

Handoffs
1