Country
—
ASN LANDING PAGE
NOANET-WA - Northwest Open Access Network
Last updated · Jul 20, 2026
Country
—
Total prefixes
66
IPv4 prefixes
61
IPv6 prefixes
5
NOANET-WA - Northwest Open Access Network currently reports 66 prefixes and 55 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
NOANET-WA - Northwest Open Access Network is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS23138
AS23138
—
AS22608
AS22608
—
AS395394
AS395394
—
AS395107
AS395107
—
AS12086
AS12086
—
AS27373
AS27373
—
AS396872
AS396872
—
AS401706
AS401706
—
AS401370
AS401370
—
AS30609
AS30609
—
AS398871
AS398871
—
AS20224
AS20224
—
AS397332
AS397332
—
AS11253
AS11253
—
AS54256
AS54256
—
AS54755
AS54755
—
AS395800
AS395800
—
AS10632
AS10632
—
AS396098
AS396098
—
AS7799
AS7799
—
AS19386
AS19386
—
AS13456
AS13456
—
AS22732
AS22732
—
AS11741
AS11741
—
AS396159
AS396159
—
AS399184
AS399184
—
AS395093
AS395093
—
AS16854
AS16854
—
AS32897
AS32897
—
AS13871
AS13871
—
AS54879
AS54879
—
AS20423
AS20423
—
AS396952
AS396952
—
AS10594
AS10594
—
AS394391
AS394391
—
AS18614
AS18614
—
AS20055
AS20055
—
AS400686
AS400686
—
AS397376
AS397376
—
AS3
AS3
—
| Prefix | Name | Country |
|---|---|---|
| 107.191.237.0/24 | AS16713 | — |
| 128.254.211.0/24 | AS16713 | — |
| 146.218.210.0/24 | AS16713 | — |
| 146.218.211.0/24 | AS16713 | — |
| 146.218.212.0/24 | AS16713 | — |
| 146.218.213.0/24 | AS16713 | — |
| 146.218.214.0/24 | AS16713 | — |
| 146.218.215.0/24 | AS16713 | — |
| 146.218.216.0/24 | AS16713 | — |
| 146.218.217.0/24 | AS16713 | — |
| 146.218.218.0/24 | AS16713 | — |
| 146.218.219.0/24 | AS16713 | — |
| 146.218.220.0/24 | AS16713 | — |
| 146.218.221.0/24 | AS16713 | — |
| 146.218.222.0/24 | AS16713 | — |
| 146.218.223.0/24 | AS16713 | — |
| 170.39.180.0/24 | AS16713 | — |
| 170.39.181.0/24 | AS16713 | — |
| 170.39.182.0/24 | AS16713 | — |
| 170.39.183.0/24 | AS16713 | — |
| 192.104.157.0/24 | AS16713 | — |
| 2001:5e0:1a::/48 | AS16713 | — |
| 2001:5e0:1d::/48 | AS16713 | — |
| 2001:5e0:21::/48 | AS16713 | — |
| 2001:5e0::/32 | AS16713 | — |
| 208.70.145.0/24 | AS16713 | — |
| 208.70.149.0/24 | AS16713 | — |
| 208.70.151.0/24 | AS16713 | — |
| 216.169.151.0/24 | AS16713 | — |
| 23.133.24.0/24 | AS16713 | — |
| 2605:b340::/32 | AS16713 | — |
| 64.113.18.0/24 | AS16713 | — |
| 64.113.19.0/24 | AS16713 | — |
| 64.113.6.0/23 | AS16713 | — |
| 64.113.8.0/24 | AS16713 | — |
| 64.146.128.0/17 | AS16713 | — |
| 64.146.138.0/24 | AS16713 | — |
| 64.146.142.0/23 | AS16713 | — |
| 64.146.144.0/24 | AS16713 | — |
| 64.146.147.0/24 | AS16713 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS16713 is an autonomous system number. The current source associates it with NOANET-WA - Northwest Open Access Network and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS16713. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS16713, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.