Autonomous System
AS16713
Last fetched
AS16713 is operated by NOANET-WA - Northwest Open Access Network, registered in US, and announces 62 prefixes to 44 BGP neighbours. AS16713 has a reputation score of 8.1 (REPUTABLE); 5 of its 66,048 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 62
- BGP neighbours
- 44
- RPKI ROAs
- 40
- MOAS conflicts
- 0
- CAIDA AS-rank
- 798
- Customer-cone ASNs
- 53
- Facilities
- 32
- Internet exchanges
- 3
- Customer degree
- 40
- Peer degree
- 21
- Provider degree
- 4
- 23.133.24.0/24
- 64.49.61.0/24
- 64.113.6.0/23
- 64.113.8.0/24
- 64.113.18.0/24
- 64.113.19.0/24
- 64.146.142.0/23
- 64.146.144.0/24
- 64.146.147.0/24
- 64.146.148.0/24
- 64.146.150.0/24
- 64.146.163.0/24
- 64.146.164.0/24
- 64.146.186.0/24
- 64.146.128.0/17
- 64.146.208.0/22
- 64.146.212.0/24
- 64.146.212.0/23
- 64.146.233.0/24
- 64.146.234.0/23
- 64.146.250.0/23
- 64.146.253.0/24
- 64.184.131.0/24
- 64.184.145.0/24
- 64.184.146.0/24
Routing posture
- Hijack posture score
- 0.03
- Route leaks
- 1
Leak types observed: TYPE3_PROVIDER_TO_PEER.
Infrastructure presence
Internet exchanges (3 total)
Facilities (32 total)
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- PTOR1
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- CSSNW Bellingham
- US Bank Building
- TierPoint Spokane
- Intergate West / Digital.forest / Fortress
- Cologix MIN1
- EdgeConneX Portland (EDCPOR01)
- Cologix MIN2
- Stack Infrastructure Portland PORO2
- Flexential - Portland/Hillsboro 2 (PDX02)
- Flexential - Portland/Hillsboro (PDX01)
- Centersquare Seattle (SEA1-B)
- H5 Data Centers Seattle
- Digital Realty Portland - PDX10
- Cologix MIN3
- Digital Fortress (PTL2)
- H5 Data Centers Portland (OR01)
- Cologix MIN4
- Sabey Intergate East Building 4
- WowRack
- Neutron - Spokane
- QTS Hillsboro (HIL1)
Route origin authorizations
A sample of 10 of this network’s 40 ROAs.
- 107.191.237.0/24 · max length /24
- 2001:5e0::/32 · max length /48
- 208.70.145.0/24 · max length /24
- 208.70.149.0/24 · max length /24
- 208.70.151.0/24 · max length /24
- 64.113.18.0/23 · max length /23
- 64.113.18.0/24 · max length /24
- 64.113.19.0/24 · max length /24
- 64.113.6.0/23 · max length /23
- 64.113.8.0/24 · max length /24
Upstreams
The networks that most often share an observed BGP path with AS16713.
Blast radius
- Announced IPv4 addresses
- 66,048
- Threat-listed addresses
- 5
- Threat density
- 0.0076 %
- Routed prefixes
- 57
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 25 of this network’s 44 BGP neighbours.
- COGENT-174 - Cogent Communications, LLC · AS174
- SHAW - Shaw Communications · AS6327
- HURRICANE - Hurricane Electric LLC · AS6939
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- OLYPENASN - Olypen, Inc. · AS7799
- CEC - Cutting Edge Communications, Inc. · AS10594
- PSE-AS - Puget Sound Energy · AS10632
- AAAWIRELESSIT - AAAWIRELESSIT · AS11253
- AS-WAVE-1 - Wave Broadband · AS11404
- BENTONREA - BENTON REA POWERNET · AS11741
- DT-MICRO - DT Micro, inc. · AS12086
- SPOWA-ASN - City of Spokane · AS13456
- TELEBYTE-NW - Telebyte NW · AS13871
- HCCU-2 - Hapo Community Credit Union · AS16854
- YAKNET - Yakima County · AS18614
- STTX-SPOKANE - Spokane Tribe Telecommunications Exchange, LLC · AS19386
- COLUMBIA-ENERGY-LLC - Columbia Energy L.L.C · AS20224
- SUQUAMISH-TRIBE - Suquamish Tribe · AS20423
- OKPUD-WA - Public Utility District No. 1 of Okanogan County · AS22608
- LINKNET - Kitsap Regional Library · AS22732
- FIRST-STEP - FIRST STEP INTERNET, LLC · AS23138
- DOUGLAS-COUNTY-COMMUNITY-NETWORK - Douglas County PUD · AS27373
- LCPUD - Lewis County PUD · AS30609
- CCPUD-NETWORKS - Chelan County Public Utility District No.1 · AS32897
- ADVANCED-STREAM-01 - Advanced Stream Inc. · AS46324
Reputation
8.1reputation score (REPUTABLE)
AS16713 (NOANET-WA - Northwest Open Access Network, US) has a reputation score of 75.7 (REPUTABLE).
- Threat density
- 82.8/100
- Graph metrics
- 90.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
- Northwest Open Access Network
- RIR
- ARIN
- Registered
- Thu, 01 Jun 2000 04:00:00 GMT
- Abuse contact
- abuse@noanet.net
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS16713 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.