Network · data from 2026-11-12
AS3944 PARTAN-LAB
Registry name: PARTAN-LAB - Partan & Partan, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3944, 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.
| 192.124.101.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 198.6.255.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 198.32.7.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
AS-SET
AS3944's PeeringDB record names no 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 7 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.124.101.0/24 | No ROA covers it. Add a ROA for AS3944, maxLength 24. |
| Route object: RIR | 192.124.101.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 198.6.255.0/24 | No ROA covers it. Add a ROA for AS3944, maxLength 24. |
| Route object: RIR | 198.6.255.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 198.32.7.0/24 | No ROA covers it. Add a ROA for AS3944, maxLength 24. |
| Route object: RIR | 198.32.7.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3944 whose prefix no peer sees AS3944 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 153.16.0.0/16 | NTTCOM | 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.