Network · data from 2026-11-12
AS396238 FairlawnGig.net
Registry name: FAIRLAWNGIG-NET - FairlawnGig.net, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396238, 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.
| 38.94.200.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 38.94.202.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 38.94.192.0/23 | No ROA | Other IRR onlyRADB | 668 99% |
| 8.2.130.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.2.186.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.40.66.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.40.68.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.42.146.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.42.148.0/23 | No ROA | RIR databaseARIN | 671 100% |
| 8.2.176.0/23 | No ROA | RIR databaseARIN | 668 99% |
| 8.226.0.0/23 | No ROA | RIR databaseARIN | 663 99% |
| 172.82.27.0/24 | Valid | Nonecovered by 172.82.24.0/22 | 670 100% |
| 23.187.120.0/24 | Valid | RIR databaseARIN | 671 100% |
| 172.82.24.0/22 | Valid | RIR databaseARIN | 670 100% |
| 2605:9fc0::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS396238: ARIN::AS-396238-CUSTOMER. 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 (AS396238 isn't in the set, or no route object for AS396238 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 | AS396238 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-396238-CUSTOMER | ARIN | 20 | 1 | Yes | 0 |
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 15 are in fix.csv.
- ROA: none11
- Route object: none1
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.94.200.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| Route object: RIR | 38.94.200.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.94.202.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| Route object: RIR | 38.94.202.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.94.192.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| Route object: RIR | 38.94.192.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 8.2.130.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.2.186.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.40.66.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.40.68.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.42.146.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.42.148.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.2.176.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| ROA: none | 8.226.0.0/23 | No ROA covers it. Add a ROA for AS396238, maxLength 23. |
| Route object: none | 172.82.27.0/24 | No route object for it. A route object for 172.82.24.0/22 with origin AS396238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396238 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS396238 is announced.
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.