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

64.20.170.0/24

2 residential-proxy exits · 30 days

Crown Castle Fiber LLC · space held by Zayo Bandwidth

Announcement
64.20.170.0/23
No RPKI
Announced by
AS46887
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
8
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4 observations

Proxy providers listing exits

  • B2Proxy
  • BESTPROXY_NET
  • BottingTools
  • Geonode
  • HELODATA
  • HPROXY
  • PROXYSCRAPE
  • RainProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
64.20.160.0/20
since Sep 2005
AS27506Internet provider7Zayo Bandwidth
64.20.160.0/19
since Oct 2006
AS27506Internet provider10Zayo Bandwidth

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
64.20.160.0/198,192ZAYO-CCF-64-20-160-0Zayo Bandwidth (ZAYOB) · USDirect AllocationApr 20, 2005abuse@zayo.com
└ 64.20.170.0/298NET-CCF--0-64-20-170-0-29unknown———
└ 64.20.170.8/304NET-CCF---64-20-170-8-30unknown———
└ 64.20.170.12/304NET-CCF-0-64-20-170-12-30unknown———
└ 64.20.170.16/298NET-CCF---64-20-170-16-29unknown———
└ 64.20.170.24/298NET-CCF--0-64-20-170-24-29unknown———
└ 64.20.170.32/2816NET-CCF---64-20-170-32-28unknown———
└ 64.20.170.48/298NET-CCF-64-20-170-48-29unknown———
└ 64.20.170.56/298NET-CCF---64-20-170-56-29unknown———
└ 64.20.170.64/298NET-CCF---64-20-170-64-29unknown———
└ 64.20.170.72/298NET-CCF---64-20-170-72-29unknown———
└ 64.20.170.80/298NET-CCF-0-64-20-170-80-29unknown———
└ 64.20.170.88/298NET-CCF-64-20-170-88-29unknown———
└ 64.20.170.96/298NET-CCF-0-64-20-170-96-29unknown———
└ 64.20.170.104/298NET-CCF-64-20-170-104-29unknown———
└ 64.20.170.112/304NET-CCF-CV119712---REVELEX-CORP-64-20-170-112-30unknown———
└ 64.20.170.116/304NET-CCF---64-20-170-116-30unknown———
└ 64.20.170.120/298NET-CCF-0-64-20-170-120-29unknown———
└ 64.20.170.128/2816NET-CCF--0-64-20-170-128-28unknown———
└ 64.20.170.144/298NET-CCF---64-20-170-144-29unknown———
└ 64.20.170.152/298NET-CCF--0-64-20-170-152-29unknown———
└ 64.20.170.160/298NET-CCF--0-64-20-170-160-29unknown———
└ 64.20.170.168/298NET-CCF--0-64-20-170-168-29unknown———
└ 64.20.170.176/298NET-CCF--0-64-20-170-176-29unknown———
└ 64.20.170.184/298NET-CCF--0-64-20-170-184-29unknown———
└ 64.20.170.192/298NET-CCF--0-64-20-170-192-29unknown———
└ 64.20.170.200/298NET-CCF--0-64-20-170-200-29unknown———
└ 64.20.170.208/298NET-CCF---64-20-170-208-29unknown———
└ 64.20.170.216/298NET-CCF--64-20-170-216-29unknown———
└ 64.20.170.224/298NET-CCF--64-20-170-224-29unknown———
└ 64.20.170.232/298NET-CCF--64-20-170-232-29unknown———
└ 64.20.170.240/304NET-CCF---64-20-170-240-30unknown———
└ 64.20.170.244/304NET-CCF--0-64-20-170-244-30unknown———
└ 64.20.170.248/298NET-CCF---64-20-170-248-29unknown———

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

64.20.170.0/23

Routing history

Pattern
Stable
First seen
Apr 2025
Current origin since
Apr 2025 · 1.6 yr
Origin networks
1