Autonomous System
AS11686
Last fetched
AS11686 is operated by ZAYO-ENA-11686 - Zayo Bandwidth, registered in US, and announces 270 prefixes to 17 BGP neighbours. AS11686 has a reputation score of 8.6 (REPUTABLE); 5 of its 734,976 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 270
- BGP neighbours
- 17
- RPKI ROAs
- 3
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,101
- Customer-cone ASNs
- 14
- Facilities
- 54
- Internet exchanges
- 8
- Customer degree
- 13
- Peer degree
- 27
- Provider degree
- 4
- 38.29.170.0/24
- 72.162.136.0/22
- 96.4.8.0/21
- 96.4.0.0/18
- 96.4.64.0/18
- 96.4.128.0/18
- 96.4.174.0/23
- 96.4.192.0/18
- 96.4.0.0/15
- 96.5.8.0/23
- 96.5.0.0/18
- 96.5.64.0/19
- 96.5.88.0/21
- 96.5.96.0/21
- 96.5.112.0/21
- 96.5.117.0/24
- 96.5.120.0/23
- 96.5.122.0/24
- 96.5.120.0/21
- 96.5.132.0/24
- 96.5.128.0/20
- 96.5.144.0/22
- 96.5.156.0/22
- 96.5.160.0/21
- 96.5.176.0/21
Infrastructure presence
Internet exchanges (8 total)
Facilities (54 total)
- Equinix DA1 - Dallas
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- Equinix CH1/CH2/CH4 - Chicago
- Equinix MI1 - Miami, NOTA
- Equinix DA3 - Dallas
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- Digital Realty ATL13 - Atlanta
- iM Critical Miami
- Netrality - Indy Telcom Center - 733 W. Henry
- Markley Group One Summer Street Boston
- Peace Communications KNX1
- CoreSite - Los Angeles (LA2)
- CoreSite - Denver (DE1)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Digital Realty CHI (350 E Cermak)
- Equinix DA4 - Dallas
- Equinix MI2 - Miami
- H5 Data Centers Nashville
- 365 Data Centers Boca Raton (BC1)
- Iron Mountain Data Center - Phoenix (AZP-1)
- QTS Miami (MIA1)
- Intergate West / Digital.forest / Fortress
- 365 Data Centers Ft. Lauderdale (FLL)
- CoreSite - Miami (MI1)
Route origin authorizations
A sample of 3 of this network’s 3 ROAs.
- 207.191.176.0/20 · max length /32
- 2610:128::/32 · max length /40
- 96.4.0.0/15 · max length /32
Upstreams
The networks that most often share an observed BGP path with AS11686.
Blast radius
- Announced IPv4 addresses
- 734,976
- Threat-listed addresses
- 5
- Threat density
- 0.0007 %
- Routed prefixes
- 264
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 17 of this network’s 17 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- HARFORDCC-AS - Harford Community College · AS6092
- ZAYO-6461 - Zayo Bandwidth · AS6461
- HURRICANE - Hurricane Electric LLC · AS6939
- AS-FRGP - University Corporation for Atmospheric Research · AS14041
- HCBE-17 - Henry County Board of Education · AS25964
- MILWAUKEE-PS - Milwaukee Public Schools · AS25971
- FORSYTH-K12-GA-US - Forsyth County Board of Education · AS40109
- CLEVELAND-MUNICIPAL-SCHOOL-DISTRICT - Cleveland Municipal School District · AS40252
- GCSSK12NET - Gainesville City Schools · AS46745
- ASN-DPSD - Denver Public Schools · AS46930
- WCPS-ASN-01 - Worcester County Public Schools · AS64248
- ESC17-AS - Education Service Center, Region 17 · AS393273
- AISD-AS - Amarillo ISD · AS393393
- ECBOCES-VNETS - East Central BOCES · AS394209
- MSDMTVERNON-IN - MSD of Mt. Vernon · AS400305
- ASN-BVSD-01 - Boulder Valley School District (BVSD) · AS401912
Reputation
8.6reputation score (REPUTABLE)
AS11686 (ZAYO-ENA-11686 - Zayo Bandwidth, US) has a reputation score of 74.1 (REPUTABLE).
- Threat density
- 85.4/100
- Graph metrics
- 80.0/100
- Historical behaviour
- 85.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- Zayo Bandwidth
- RIR
- ARIN
- Registered
- Mon, 16 Nov 1998 05:00:00 GMT
- Abuse contact
- abuse@zayo.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS11686 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.