Network · data from 2026-11-12
AS3931 LOGICAL - Logical Net Corporation
Registry name: LOGICAL - Logical Net Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3931, 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.
| 209.23.101.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 209.23.102.0/23 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 209.23.104.0/21 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 209.23.112.0/20 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 216.230.160.0/20 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS3931 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 6 are in fix.csv.
- ROA: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.23.101.0/24 | No ROA covers it. Add a ROA for AS3931, maxLength 24. |
| ROA: none | 209.23.102.0/23 | No ROA covers it. Add a ROA for AS3931, maxLength 23. |
| ROA: none | 209.23.104.0/21 | No ROA covers it. Add a ROA for AS3931, maxLength 21. |
| ROA: none | 209.23.112.0/20 | No ROA covers it. Add a ROA for AS3931, maxLength 20. |
| ROA: none | 216.230.160.0/20 | No ROA covers it. Add a ROA for AS3931, maxLength 20. |
Route objects not announced
Route objects with origin AS3931 whose prefix no peer sees AS3931 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2607:f908::/32 | ALTDB, ARIN, 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.