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

67.208.172.0/22

6 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
6
0.59% of its addresses · 30 days
Always-on exits
2
33% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
42
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

13K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
67.208.172.0/2425
67.208.173.0/2401

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • ColaProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
67.208.160.0/19
since Nov 2021
AS46887Internet provider16
4 always on
Zayo Bandwidth
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
67.208.174.0/24
since Sep 2021
AS46887UnknownZayo 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
67.208.160.0/198,192ZAYO-CCF-67-208-160-0Zayo Bandwidth (ZAYOB) · USDirect AllocationJul 16, 2007abuse@zayo.com
└ 67.208.172.0/2664NET-CCF---67-208-172-0-26unknown———
└ 67.208.172.68/304NET-Z-CCF--67-208-172-68-30unknown———
└ 67.208.172.72/298NET-CCF---67-208-172-72-29unknown———
└ 67.208.172.80/298NET-CCF---67-208-172-80-29unknown———
└ 67.208.172.88/298NET-CCF--0-67-208-172-88-29unknown———
└ 67.208.172.96/298NET-CCF--0-67-208-172-96-29unknown———
└ 67.208.172.104/304NET-CCF--0-67-208-172-104-30unknown———
└ 67.208.172.108/304NET-CCF--0-67-208-172-108-30unknown———
└ 67.208.172.112/298NET-CCF---67-208-172-112-29unknown———
└ 67.208.172.120/298NET-CCF---67-208-172-120-29unknown———
└ 67.208.172.128/2732NET-CCF--LT-292-67-208-172-128-27unknown———
└ 67.208.172.160/298NET-CCF--0-67-208-172-160-29unknown———
└ 67.208.172.176/304NET-CCF---67-208-172-176-30unknown———
└ 67.208.172.180/304NET-CCF--0-67-208-172-180-30unknown———
└ 67.208.172.184/298NET-CCF---67-208-172-184-29unknown———
└ 67.208.172.192/298NET-CCF--0-67-208-172-192-29unknown———
└ 67.208.172.200/298NET-CCF-0-67-208-172-200-29unknown———
└ 67.208.172.208/2816NET-CCF---67-208-172-208-28unknown———
└ 67.208.172.224/304NET-CCF---67-208-172-224-30unknown———
└ 67.208.172.228/304NET-CCF---67-208-172-228-30unknown———
└ 67.208.172.232/304NET-CCF---67-208-172-232-30unknown———
└ 67.208.172.236/304NET-CCF--LT-292-67-208-172-236-30unknown———
└ 67.208.172.240/304NET-CCF---67-208-172-240-30unknown———
└ 67.208.172.244/304NET-CCF---67-208-172-244-30unknown———
└ 67.208.172.248/304NET-CCF---67-208-172-248-30unknown———
└ 67.208.172.252/304NET-CCF---67-208-172-252-30unknown———
└ 67.208.173.0/2816NET-CCF---67-208-173-0-28unknown———
└ 67.208.173.16/298NET-CCF---67-208-173-16-29unknown———
└ 67.208.173.24/298NET-CCF---67-208-173-24-29unknown———
└ 67.208.173.32/298NET-CCF---67-208-173-32-29unknown———
└ 67.208.173.40/298NET-CCF---67-208-173-40-29unknown———
└ 67.208.173.48/298NET-CCF---67-208-173-48-29unknown———
└ 67.208.173.56/298NET-CCF--0-67-208-173-56-29unknown———
└ 67.208.173.64/304NET-CCF--0-67-208-173-64-30unknown———
└ 67.208.173.68/304NET-CCF--67-208-173-68-30unknown———
└ 67.208.173.72/298NET-CCF---67-208-173-72-29unknown———
└ 67.208.173.80/304NET-CCF---67-208-173-80-30unknown———
└ 67.208.173.84/304NET-CCF---67-208-173-84-30unknown———
└ 67.208.173.88/298NET-CCF---67-208-173-88-29unknown———
└ 67.208.173.96/304NET-CCF---67-208-173-96-30unknown———
└ 67.208.173.100/304NET-CCF--0-67-208-173-100-30unknown———
└ 67.208.173.104/298NET-CCF---67-208-173-104-29unknown———
└ 67.208.173.112/298NET-CCF---67-208-173-112-29unknown———
└ 67.208.173.120/298NET-CCF---67-208-173-120-29unknown———
└ 67.208.173.128/2732NET-Z-CCF--67-208-173-128-27unknown———
└ 67.208.173.160/2732NET-CCF---67-208-173-160-27unknown———
└ 67.208.173.192/2732NET-CCF---67-208-173-192-27unknown———
└ 67.208.173.224/298NET-CCF---67-208-173-224-29unknown———
└ 67.208.173.232/298NET-Z-CCF--67-208-173-232-29unknown———
└ 67.208.173.240/298NET-CCF--0-67-208-173-240-29unknown———
└ 67.208.173.248/304NET-CCF---67-208-173-248-30unknown———
└ 67.208.173.252/304NET-CCF--0-67-208-173-252-30unknown———
└ 67.208.174.0/24256NET-SD-67-208-174-0-24Market News International, Inc. (fka Need to Know News, LLC) (C05689009) · USReassignedApr 20, 2015abuse@zayo.com
via ZAYO-CCF-67-208-160-0
└ 67.208.175.0/298NET-CCF---67-208-175-0-29unknown———
└ 67.208.175.8/298NET-CCF---67-208-175-8-29unknown———
└ 67.208.175.16/2816NET-CCF---67-208-175-16-28unknown———
└ 67.208.175.32/298NET-CCF--0-67-208-175-32-29unknown———
└ 67.208.175.40/298NET-CCF--0-67-208-175-40-29unknown———
└ 67.208.175.48/298NET-CCF---67-208-175-48-29unknown———
└ 67.208.175.56/298NET-CCF---67-208-175-56-29unknown———
└ 67.208.175.64/298NET-CCF---67-208-175-64-29unknown———
└ 67.208.175.72/298NET-CCF---67-208-175-72-29unknown———
└ 67.208.175.80/298NET-CCF--0-67-208-175-80-29unknown———
└ 67.208.175.88/298NET-CCF--SD-49981-67-208-175-88-29unknown———
└ 67.208.175.96/2732NET-CCF---67-208-175-96-27unknown———
└ 67.208.175.128/25128NET-CCF--0-67-208-175-128-25unknown———

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

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
Unknown25625%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
Apr 2009
Current origin since
Sep 2021 · 5.1 yr
Origin networks
3
Last change of origin
Sep 2021
Recorded history

History

Handoffs
2