Data as of Nov 13, 2026

64.17.96.0/19

1 residential-proxy exit · 30 days

FirstLight Fiber, Inc. · space held by FirstLight Networks, LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
94% of it

Residential-proxy exits

Proxy exits
1
0.01% of its addresses · 30 days
Spread
1 of 32
/24s with at least one exit
Providers
1
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • AnyIP

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
64.17.97.0/24
since Jun 2017
AS54989ResidentialFirstLight Networks, LLC
64.17.119.0/24
since Jun 2017
AS54989ResidentialFirstLight Networks, LLC

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
64.17.96.0/198,192FLNET-12FirstLight Networks, LLC (FNL-76) · USDirect AllocationApr 16, 2002ipabuse@firstlight.net
└ 64.17.97.0/24256SOVER-DUNCABLE-11unknownReassignedDec 17, 2012ipabuse@firstlight.net
via FLNET-12
└ 64.17.99.0/24256SOVER-SVBCunknown———
└ 64.17.101.0/24256SOVER-BVTSCONNunknown———
└ 64.17.101.0/24256SOVER-BVTSCONNunknown———
└ 64.17.102.32/29864-17-102-32-29unknown———
└ 64.17.102.64/29864-17-102-64-29unknown———
└ 64.17.102.80/29864-17-102-80-29unknown———
└ 64.17.102.88/29864-17-102-88-29unknown———
└ 64.17.102.96/29864-17-102-96-29unknown———
└ 64.17.102.104/29864-17-102-104-29unknown———
└ 64.17.102.120/29864-17-102-120-29unknown———
└ 64.17.102.144/29864-17-102-144-29unknown———
└ 64.17.102.152/29864-17-102-152-29unknown———
└ 64.17.102.168/29864-17-102-168-29unknown———
└ 64.17.102.176/29864-17-102-176-29unknown———
└ 64.17.102.184/29864-17-102-184-29unknown———
└ 64.17.102.208/29864-17-102-208-29unknown———
└ 64.17.102.216/29864-17-102-216-29unknown———
└ 64.17.102.224/29864-17-102-224-29unknown———
└ 64.17.102.232/29864-17-102-232-29unknown———
└ 64.17.102.240/281664-17-102-240-28unknown———
└ 64.17.103.12/30464-17-103-12-30unknown———
└ 64.17.103.16/29864-17-103-16-29unknown———
└ 64.17.103.32/29864-17-103-32-29unknown———
└ 64.17.103.40/29864-17-103-40-29unknown———
└ 64.17.103.56/29864-17-103-56-29unknown———
└ 64.17.103.64/29864-17-103-64-29unknown———
└ 64.17.103.72/29864-17-103-72-29unknown———
└ 64.17.103.80/30464-17-103-80-30unknown———
└ 64.17.103.84/30464-17-103-84-30unknown———
└ 64.17.103.88/30464-17-103-88-30unknown———
└ 64.17.103.92/30464-17-103-92-30unknown———
└ 64.17.103.96/30464-17-103-96-30unknown———
└ 64.17.103.104/29864-17-103-104-29unknown———
└ 64.17.103.112/30464-17-103-112-30unknown———
└ 64.17.116.16/2816SOVER-HBMFIB-GW2unknown———
└ 64.17.116.32/298SOVER-BRTTOWER-GWunknown———
└ 64.17.116.56/298SOVER-BUHSunknown———
└ 64.17.116.80/2816SOVER-802TOYOunknown———
└ 64.17.116.96/298SOVER-WCWINCunknown———
└ 64.17.116.104/298SOVER-MERRILLG-2unknown———
└ 64.17.116.112/2816SOVER-WINDSPD-GW3unknown———
└ 64.17.116.128/25128SOVER-OCSU-3unknown———
└ 64.17.117.0/2816SOVER-JEDI-LANunknown———
└ 64.17.117.16/2816SOVER-AMPDSL1unknown———
└ 64.17.117.32/2732SOVER-HBINSUREunknown———
└ 64.17.117.80/2816SOVER-NEAIRSYSunknown———
└ 64.17.117.104/298SOVER-AUTOSPOR-GWunknown———
└ 64.17.117.120/298SOVER-TECHV-GWunknown———
└ 64.17.117.128/2732SOVER-KWAVEunknown———
└ 64.17.117.192/2732SOVER-VPBSCOLunknown———
└ 64.17.117.224/2732SOVER-BEDEX-2unknown———
└ 64.17.119.0/24256SOVER-DUNCABLE-8Duncan Cable (C02054022) · USReassignedSep 29, 2008ipabuse@firstlight.net
via FLNET-12
└ 64.17.125.0/24256SOVER-VTWEB-1unknown———
└ 64.17.127.8/298SOVER-HRBLOCK2unknown———
└ 64.17.127.16/2816SOVER-MINUTEMANunknown———
└ 64.17.127.64/2732SOVER-HAMPINNunknown———
└ 64.17.127.100/304SOVER-DATAIIunknown———
└ 64.17.127.112/2816SOVER-BANKBENNunknown———
└ 64.17.127.128/298SOVER-ARLINGTON-GWunknown———
└ 64.17.127.136/298SOVER-CVSUDIA-GWunknown———
└ 64.17.127.144/29864-17-127-144-29unknown———
└ 64.17.127.152/298SOVER-HOLSTE3unknown———
└ 64.17.127.160/2816SOVER-ROVTECH-2unknown———
└ 64.17.127.224/298SOVER-HPBXBCCHunknown———

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

8,192 addresses
TypeAddressesShareRanges
Business7,68094%3
Residential5126.3%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
2
Last change of origin
Dec 2018
Recorded history

History

Handoffs
1