Network · data from 2026-11-12
AS397672 Wyoming Wireless Internet
Registry name: AS-WYOMINGWIRELESS - Wyoming Wireless Internet, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397672, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 67.130.74.0/24 | No ROA | None | 670 100% |
| 204.131.236.0/24 | No ROA | None | 670 100% |
| 204.132.112.0/24 | No ROA | None | 670 100% |
| 192.122.212.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 136.175.157.0/24 | No ROA | RIR databaseARIN | 669 99% |
| 23.173.224.0/24 | Valid | RIR databaseARIN | 670 100% |
| 23.173.224.0/23 | Valid | RIR databaseARIN | 669 99% |
| 23.173.225.0/24 | Valid | RIR databaseARIN | 669 99% |
| 2602:fe06::/36 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS397672: AS397672:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS397672 isn't in the set, or no route object for AS397672 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS397672 in it | Not covered |
|---|---|---|---|---|---|
| AS397672:AS-ALL | ARIN | 2 | 1 | Yes | 3 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 67.130.74.0/24 | No ROA covers it. Add a ROA for AS397672, maxLength 24. |
| Route object: none | 67.130.74.0/24 | No route object for it. Add a route object with origin AS397672 in the RIR database for the space. |
| ROA: none | 204.131.236.0/24 | No ROA covers it. Add a ROA for AS397672, maxLength 24. |
| Route object: none | 204.131.236.0/24 | No route object for it. Add a route object with origin AS397672 in the RIR database for the space. |
| ROA: none | 204.132.112.0/24 | No ROA covers it. Add a ROA for AS397672, maxLength 24. |
| Route object: none | 204.132.112.0/24 | No route object for it. Add a route object with origin AS397672 in the RIR database for the space. |
| ROA: none | 192.122.212.0/24 | No ROA covers it. Add a ROA for AS397672, maxLength 24. |
| ROA: none | 136.175.157.0/24 | No ROA covers it. Add a ROA for AS397672, maxLength 24. |
Route objects not announced
Route objects with origin AS397672 whose prefix no peer sees AS397672 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:318::/48 | ARIN | Valid |
| 2602:fe06:1::/48 | ARIN | Valid |
| 2602:fe06:2::/47 | ARIN | Valid |
| 2602:fe06:100::/40 | ARIN | Valid |
| 2602:fe06:200::/40 | ARIN | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.