Network · data from 2026-11-12
AS7663 FUJIMIC
Registry name: FFNET - FUJI NEXTERA LABO INC., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7663, 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.
| 210.167.32.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.34.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.35.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.40.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.41.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.42.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.43.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.51.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.52.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.62.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 210.167.63.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
AS-SET
AS7663'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 44 are in fix.csv.
- ROA: none11
- Route object: RIR11
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 210.167.32.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.32.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.34.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.34.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.35.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.35.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.40.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.40.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.41.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.41.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.42.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.42.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.43.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.43.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.51.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.51.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.52.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.62.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.62.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 210.167.63.0/24 | No ROA covers it. Add a ROA for AS7663, maxLength 24. |
| Route object: RIR | 210.167.63.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7663 whose prefix no peer sees AS7663 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 210.167.32.0/19 | JPIRR, RADB | No ROA |
| 210.167.33.0/24 | NTTCOM, RADB | No ROA |
| 210.167.36.0/24 | NTTCOM, RADB | No ROA |
| 210.167.37.0/24 | NTTCOM, RADB | No ROA |
| 210.167.38.0/24 | NTTCOM, RADB | No ROA |
| 210.167.39.0/24 | NTTCOM, RADB | No ROA |
| 210.167.44.0/24 | NTTCOM, RADB | No ROA |
| 210.167.45.0/24 | NTTCOM, RADB | No ROA |
| 210.167.46.0/24 | NTTCOM, RADB | No ROA |
| 210.167.47.0/24 | NTTCOM, RADB | No ROA |
| 210.167.48.0/24 | NTTCOM, RADB | No ROA |
| 210.167.49.0/24 | NTTCOM, RADB | No ROA |
| 210.167.50.0/24 | NTTCOM, RADB | No ROA |
| 210.167.53.0/24 | NTTCOM, RADB | No ROA |
| 210.167.54.0/24 | NTTCOM, RADB | No ROA |
| 210.167.55.0/24 | NTTCOM, RADB | No ROA |
| 210.167.56.0/24 | NTTCOM, RADB | No ROA |
| 210.167.57.0/24 | NTTCOM, RADB | No ROA |
| 210.167.58.0/24 | NTTCOM, RADB | No ROA |
| 210.167.59.0/24 | NTTCOM, RADB | No ROA |
| 210.167.60.0/24 | NTTCOM, RADB | No ROA |
| 210.167.61.0/24 | NTTCOM, 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.