Network · data from 2026-11-12
AS400097 NATIONALWIFI
Registry name: NATIONALWIFI - National Wi-Fi, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400097, 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.
| 207.207.193.0/24 | No ROA | None | 673 100% |
| 2606:3d40:3b09::/48 | No ROA | None | 635 100% |
| 2606:3d40:3b02::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 2606:3d40:5301::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 2606:3d40:9::/48 | No ROA | Other IRR onlyRADB | 631 99% |
| 2606:3d40:4c00::/48 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 103.123.221.0/24 | Valid | Nonecovered by 103.123.220.0/22 | 673 100% |
| 103.123.222.0/24 | Valid | Nonecovered by 103.123.220.0/22 | 673 100% |
| 103.123.220.0/24 | Valid | Nonecovered by 103.123.220.0/22 | 672 100% |
| 2606:3d40:2::/48 | Valid | None | 636 100% |
| 2606:3d40:3::/48 | Valid | None | 636 100% |
| 2606:3d40:3402::/48 | Valid | None | 636 100% |
| 2606:3d40:3403::/48 | Valid | None | 636 100% |
| 2606:3d40:5200::/48 | Valid | None | 636 100% |
| 2606:3d40:6::/48 | Valid | None | 635 100% |
| 2606:3d40:d::/48 | Valid | None | 635 100% |
| 2606:3d40:15::/48 | Valid | None | 635 100% |
| 2606:3d40:3400::/48 | Valid | None | 635 100% |
| 2606:3d40:3b00::/48 | Valid | None | 635 100% |
| 2606:3d40:5d03::/48 | Valid | None | 635 100% |
| 2606:3d40:f::/48 | Valid | None | 634 100% |
| 103.123.223.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 2606:3d40:10::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2606:3d40:5d00::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2606:3d40:7::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:8::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:a::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:14::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:16::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:5d01::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:5d02::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2606:3d40:5::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2606:3d40:13::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2606:3d40:1a::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 2606:3d40:4d01::/48 | Valid | RIR databaseARIN | 636 100% |
| 2606:3d40:3702::/48 | Valid | RIR databaseARIN | 635 100% |
| 2606:3d40:3705::/48 | Valid | RIR databaseARIN | 635 100% |
| 2606:3d40:3b05::/48 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2606:3d40:3c00::/48 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2606:3d40:5d06::/48 | Valid | RIR databaseARIN | 635 100% |
| 2606:3d40:4000::/48 | Valid | RIR databaseARIN | 634 100% |
| 2606:3d40:5d05::/48 | Valid | RIR databaseARIN, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS400097: AS-NATWIFI. 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 (AS400097 isn't in the set, or no route object for AS400097 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 | AS400097 in it | Not covered |
|---|---|---|---|---|---|
| AS-NATWIFI | ARIN | 1 | 1 | Yes | 14 |
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 57 are in fix.csv.
- ROA: none6
- Route object: none17
- Route object: RIR17
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.207.193.0/24 | No ROA covers it. Add a ROA for AS400097, maxLength 24. |
| Route object: none | 207.207.193.0/24 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| ROA: none | 2606:3d40:3b09::/48 | No ROA covers it. Add a ROA for AS400097, maxLength 48. |
| Route object: none | 2606:3d40:3b09::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| ROA: none | 2606:3d40:3b02::/48 | No ROA covers it. Add a ROA for AS400097, maxLength 48. |
| Route object: RIR | 2606:3d40:3b02::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:3d40:5301::/48 | No ROA covers it. Add a ROA for AS400097, maxLength 48. |
| Route object: RIR | 2606:3d40:5301::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:3d40:9::/48 | No ROA covers it. Add a ROA for AS400097, maxLength 48. |
| Route object: RIR | 2606:3d40:9::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:3d40:4c00::/48 | No ROA covers it. Add a ROA for AS400097, maxLength 48. |
| Route object: RIR | 2606:3d40:4c00::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 103.123.221.0/24 | No route object for it. A route object for 103.123.220.0/22 with origin AS400097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 103.123.222.0/24 | No route object for it. A route object for 103.123.220.0/22 with origin AS400097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 103.123.220.0/24 | No route object for it. A route object for 103.123.220.0/22 with origin AS400097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:2::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:3::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:3402::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:3403::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:5200::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:6::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:d::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:15::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:3400::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:3b00::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:5d03::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: none | 2606:3d40:f::/48 | No route object for it. Add a route object with origin AS400097 in the RIR database for the space. |
| Route object: RIR | 103.123.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:10::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:5d00::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:7::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:8::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:14::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:16::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:5d01::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:5d02::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:5::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:13::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2606:3d40:1a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400097 whose prefix no peer sees AS400097 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.165.128.0/24 | RADB | No ROA |
| 103.123.220.0/22 | RADB | No ROA |
| 2604:37c0::/32 | RADB | No ROA |
| 2606:3d40:12::/48 | RADB | Valid |
| 2606:3d40:19::/48 | RADB | Valid |
| 2606:3d40:3b06::/48 | ARIN | Valid |
| 2606:3d40:3c02::/48 | RADB | No ROA |
| 2606:3d40:4d02::/48 | RADB | No ROA |
| 2606:3d40:4d03::/48 | RADB | No ROA |
| 2606:3d40:4d04::/48 | RADB | No ROA |
| 2606:3d40:4d05::/48 | RADB | No ROA |
| 2606:3d40:4f00::/48 | ARIN | Valid |
| 2606:3d40:4f01::/48 | RADB | No ROA |
| 2606:3d40:5d04::/48 | RADB | Valid |
| 2606:3d40:5d08::/48 | ARIN | Valid |
| 2606:3d40:5d0b::/48 | RADB | No ROA |
| 2606:3d40:6000::/48 | RADB | No ROA |
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.