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

207.181.64.0/18

No anonymizer space · no proxy exits in 30 days

Zayo Bandwidth

Announcement
this exact prefix
RPKI valid
Announced by
AS6461
Type
Internet provider
83% of it

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
207.181.66.0/24
since Apr 2021
AS15290Internet providerZayo Bandwidth
207.181.106.0/24
since Apr 2021
AS15290UnknownZayo 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
207.181.64.0/1816,384ZAYO-CAN-11Zayo Bandwidth (ZAYOB) · USDirect AllocationAug 29, 1996abuse@zayo.com
└ 207.181.70.28/304NET-0-207-181-70-28-30unknown———
└ 207.181.70.32/298NET-207-181-70-32-29unknown———
└ 207.181.70.40/298NET-0-207-181-70-40-29unknown———
└ 207.181.71.96/304NET-207-181-71-96-30unknown———
└ 207.181.86.0/2664NET-207-181-86-0-26unknown———
└ 207.181.106.0/24256NET-IDIA-238243-207-181-106-0-24Computer Idol (C11366823) · CAReassignedSep 24, 2025abuse@zayo.com
via ZAYO-CAN-11
└ 207.181.107.0/304NET-207-181-107-0-30unknown———
└ 207.181.107.16/298NET-207-181-107-16-29unknown———
└ 207.181.107.56/298NET-207-181-107-56-29unknown———
└ 207.181.107.176/304NET-207-181-107-176-30unknown———
└ 207.181.107.184/298NET-207-181-107-184-29unknown———
└ 207.181.110.0/2732NETCOM-GLENNIE-Sunknown———
└ 207.181.110.32/2732NETCOM-HOMESTAKEunknown———
└ 207.181.110.96/2732NETCOM-ALTIMEDunknown———
└ 207.181.111.32/2732NETCOM-PHXunknown———
└ 207.181.111.64/2664NETCOM-UNIGLOBEunknown———
└ 207.181.111.128/2732NETCOM-DELTA-CREDITunknown———
└ 207.181.111.160/2732NETCOM-AMESunknown———
└ 207.181.111.192/2732NETCOM-ROYALBANK-1unknown———
└ 207.181.111.224/2732NETCOM-DAVREY-2unknown———
└ 207.181.113.0/24256NETCOM-ACTIVEunknown———
└ 207.181.116.0/24256NETCOM-CLOCKWORXunknown———
└ 207.181.117.32/2732NETCOM-ONTCHILDunknown———
└ 207.181.117.64/2732NETCOM-CARPETONE-1unknown———
└ 207.181.117.96/2732NETCOM-DIGITAL-LINKunknown———
└ 207.181.117.128/2732NETCOM-GUARANTYunknown———
└ 207.181.117.160/2732NETCOM-PARTS-HEADQunknown———
└ 207.181.118.32/2732NET-207-181-118-32-27unknown———
└ 207.181.118.64/2732NETCOM-SOFTMOSISunknown———
└ 207.181.118.96/2732NETCOM-INNOVATIONunknown———
└ 207.181.118.128/2732NETCOM-TELCOMunknown———
└ 207.181.118.160/2732NETCOM-PUBLISHINGunknown———
└ 207.181.118.192/2732NETCOM-INSTANTIATEDunknown———
└ 207.181.118.224/2732NETCOM-BITHEADSunknown———
└ 207.181.119.32/2732NETCOM-THEROCunknown———
└ 207.181.119.128/2732NETCOM-FOOTMAXunknown———
└ 207.181.119.160/2732NETCOM-BLOCKADEunknown———
└ 207.181.119.192/2732NETCOM-GALAXY-SATunknown———
└ 207.181.119.224/2732NETCOM-NUMBERTELunknown———
└ 207.181.120.0/24256NETCOM-HELICONunknown———
└ 207.181.121.32/2732NETCOM-DAVIS-1unknown———
└ 207.181.121.96/2732NETCOM-MAYAunknown———
└ 207.181.121.128/2732NETCOM-CANDERELunknown———
└ 207.181.121.160/2732NETCOM-ALTHIN-BIOunknown———
└ 207.181.121.192/2732NETCOM-HIGHER-SOURCEunknown———
└ 207.181.121.224/2732NETCOM-RICHTER-MGMTunknown———
└ 207.181.122.0/24256NETCOM-DOLFINunknown———
└ 207.181.123.0/24256NETCOM-METRONETunknown———
└ 207.181.124.0/2732NETCOM-FITunknown———
└ 207.181.124.32/2732NETCOM-NERAYunknown———
└ 207.181.124.64/2732NETCOM-IVEYunknown———
└ 207.181.124.96/2732NETCOM-GENXunknown———
└ 207.181.124.128/2732NETCOM-MYANGELunknown———
└ 207.181.124.160/2732NETCOM-COLLECT-2unknown———
└ 207.181.124.192/2732NETCOM-ANDERSONunknown———
└ 207.181.124.224 - 207.181.124.25431NETCOM-DRUGunknown———
└ 207.181.125.64/2664NETCOM-BIONDANunknown———
└ 207.181.125.128/2732NETCOM-TRI-ADunknown———
└ 207.181.125.160/2732NETCOM-IDSGROUPunknown———
└ 207.181.125.192/2732NETCOM-DELPHIunknown———
└ 207.181.125.224/2732NETCOM-OPALSKYunknown———
└ 207.181.126.0/24256NETCOM-RICHTERunknown———
└ 207.181.127.128/2732NETCOM-VISIONFACTORYunknown———
└ 207.181.127.160/2732NETCOM-EMPLASTICunknown———
└ 207.181.127.192/2732NETCOM-TABLECHARMunknown———

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

16,384 addresses
TypeAddressesShareRanges
Internet provider13,53783%20
Business1,5679.6%47
Residential1,0246.3%4
Unknown2561.6%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2021 · 5.5 yr
Origin networks
2
Last change of origin
May 2021
Recorded history

History

Handoffs
1