Network · data from 2026-11-12
AS207645 FWNETWORKS-AS F & W Networks Ltd
Registry name: FWNETWORKS-AS F & W Networks Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207645, 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.
| 5.83.200.0/24 | Invalid: maxLength | Nonecovered by 5.83.192.0/20 | 126 19% |
| 5.83.201.0/24 | Invalid: maxLength | Nonecovered by 5.83.192.0/20 | 126 19% |
| 38.9.8.0/23 | No ROA | Other IRR onlyRADB | 669 99% |
| 38.9.10.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 38.9.11.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 31.214.156.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 5.181.99.0/24 | No ROA | RIR databaseRIPE | 668 99% |
| 5.83.192.0/20 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 37.148.220.0/22 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 82.153.74.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 82.153.76.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 87.254.0.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 94.176.96.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 166.1.120.0/21 | Valid | RIR databaseARIN | 669 99% |
| 185.86.10.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.190.92.0/22 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 193.28.11.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.120.133.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 209.240.0.0/22 | Valid | RIR databaseARIN, RADB | 669 99% |
| 45.137.18.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0d:b100::/29 | Valid | RIR databaseRIPE | 604 95% |
| 209.240.4.0/22 | Valid | RIR databaseARIN, RADB | 4 1%low visibility |
| 80.249.128.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS207645 isn't in PeeringDB, where networks name their AS-SET.
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 14 are in fix.csv.
- ROA: maxLength2
- ROA: none5
- Route object: none2
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 5.83.200.0/24 | ROA 5.83.192.0/20 AS207645 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 5.83.200.0/24. |
| Route object: none | 5.83.200.0/24 | No route object for it. A route object for 5.83.192.0/20 with origin AS207645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207645 in the RIR database for the space. |
| ROA: maxLength | 5.83.201.0/24 | ROA 5.83.192.0/20 AS207645 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 5.83.201.0/24. |
| Route object: none | 5.83.201.0/24 | No route object for it. A route object for 5.83.192.0/20 with origin AS207645 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207645 in the RIR database for the space. |
| ROA: none | 38.9.8.0/23 | No ROA covers it. Add a ROA for AS207645, maxLength 23. |
| Route object: RIR | 38.9.8.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.9.10.0/24 | No ROA covers it. Add a ROA for AS207645, maxLength 24. |
| Route object: RIR | 38.9.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.9.11.0/24 | No ROA covers it. Add a ROA for AS207645, maxLength 24. |
| Route object: RIR | 38.9.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 31.214.156.0/24 | No ROA covers it. Add a ROA for AS207645, maxLength 24. |
| ROA: none | 5.181.99.0/24 | No ROA covers it. Add a ROA for AS207645, maxLength 24. |
Route objects not announced
Route objects with origin AS207645 whose prefix no peer sees AS207645 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.9.8.0/22 | RADB | No ROA |
| 2a0d:a200::/29 | RIPE | 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.