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

160.72.52.0/22

4 residential-proxy exits · 30 days

Crown Castle Fiber LLC · space held by Zayo Bandwidth

Announcement
this exact prefix
No RPKI
Announced by
AS46887
Type
Internet provider
75% of it

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
22
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

302 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
160.72.53.0/2403
160.72.52.0/2401

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BlurPath
  • CliProxy
  • ColaProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GloryCloud
  • IPPeak
  • LudaxProxy
  • NovaProxy
  • PrivateByte
  • ProxyEmpire
  • RainProxy
  • RapidProxy
  • Thordata
  • VantageProxies
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
160.72.48.0/20
since Sep 2021
AS46887Internet provider9
1 always on
Zayo Bandwidth
160.72.32.0/19
since Sep 2021
AS46887Internet provider14
1 always on
Zayo Bandwidth
160.72.0.0/16
since Nov 2021
AS46887Internet provider88
8 always on
Zayo Bandwidth
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
160.72.54.0/24
since Oct 2025
AS401539HostingZayo Bandwidth

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
160.72.0.0/1665,536ZAYO-CCF-160-72-0-0Zayo Bandwidth (ZAYOB) · USDirect AllocationApr 29, 2016abuse@zayo.com
└ 160.72.52.0/298LTF-SD-51079-160-72-52-0-29unknown———
└ 160.72.52.8/298LTF-SD-51079-160-72-52-8-29unknown———
└ 160.72.52.16/298LTF--160-72-52-16-29unknown———
└ 160.72.52.24/298LTF--160-72-52-24-29unknown———
└ 160.72.52.32/2732LTF--160-72-52-32-27unknown———
└ 160.72.52.64/2732LTF--160-72-52-64-27unknown———
└ 160.72.52.96/298LTF-LT-187-160-72-52-96-29unknown———
└ 160.72.52.104/298LTF--160-72-52-104-29unknown———
└ 160.72.52.112/298LTF-0-160-72-52-112-29unknown———
└ 160.72.52.120/298LTF--160-72-52-120-29unknown———
└ 160.72.52.140/304NET-CCF--160-72-52-140-30unknown———
└ 160.72.52.144/2816LTF--160-72-52-144-28unknown———
└ 160.72.52.160/298LTF-0-160-72-52-160-29unknown———
└ 160.72.52.168/298LTF--160-72-52-168-29unknown———
└ 160.72.52.192/2732NET-CCF--0-160-72-52-192-27unknown———
└ 160.72.52.224/298NET-CCF--0-160-72-52-224-29unknown———
└ 160.72.52.240/298NET-CCF-0-160-72-52-240-29unknown———
└ 160.72.52.248/298LTF--160-72-52-248-29unknown———
└ 160.72.53.0/298LTF-0-160-72-53-0-29unknown———
└ 160.72.53.8/298LTF--160-72-53-8-29unknown———
└ 160.72.53.16/298NET-CCF-0-160-72-53-16-29unknown———
└ 160.72.53.24/298NET-CCF--160-72-53-24-29unknown———
└ 160.72.53.32/298LTF--160-72-53-32-29unknown———
└ 160.72.53.48/298LTF--160-72-53-48-29unknown———
└ 160.72.53.56/298LTF--160-72-53-56-29unknown———
└ 160.72.53.64/298LTF--160-72-53-64-29unknown———
└ 160.72.53.72/298LTF--160-72-53-72-29unknown———
└ 160.72.53.80/2816LTF--160-72-53-80-28unknown———
└ 160.72.53.96/2732LTF--160-72-53-96-27unknown———
└ 160.72.53.132/304NET-CCF---160-72-53-132-30unknown———
└ 160.72.53.136/304NET-Z-CCF--160-72-53-136-30unknown———
└ 160.72.53.144/298LTF--160-72-53-144-29unknown———
└ 160.72.53.160/2732LTF--160-72-53-160-27unknown———
└ 160.72.53.192/298LTF-168054-INET-CCF---METTEL-160-72-53-192-29unknown———
└ 160.72.53.200/304NET-CCF-0-160-72-53-200-30unknown———
└ 160.72.53.208/2816LTF-0-160-72-53-208-28unknown———
└ 160.72.53.224/2732LTF-LT-292-160-72-53-224-27unknown———
└ 160.72.54.0/25128NET-CCF---160-72-54-0-25unknown———
└ 160.72.54.128/25128NET-CCF---160-72-54-128-25unknown———
└ 160.72.55.0/24256LTF-160-72-55-0-24unknown———

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

1,024 addresses
TypeAddressesShareRanges
Internet provider76875%2
Hosting25625%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2025
Current origin since
Jan 2025 · 1.8 yr
Origin networks
1