Network · data from 2026-11-12
AS9425 FITI-AS-BKB2 - Future Internet Technology Infrastructure (FITI)
Registry name: FITI-AS-BKB2 - Future Internet Technology Infrastructure (FITI), CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9425, 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.
| 2401:34a0::/32 | Valid | None | 636 100% |
| 2401:34a1::/32 | Valid | None | 636 100% |
AS-SET
AS9425 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 42 are in fix.csv.
- Route object: none2
- Route object: not announced40
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2401:34a0::/32 | No route object for it. Add a route object with origin AS9425 in the RIR database for the space. |
| Route object: none | 2401:34a1::/32 | No route object for it. Add a route object with origin AS9425 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9425 whose prefix no peer sees AS9425 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.61.64.0/19 | RADB | No ROA |
| 202.61.68.0/24 | NTTCOM | No ROA |
| 202.61.69.0/24 | NTTCOM | No ROA |
| 202.61.70.0/24 | NTTCOM | No ROA |
| 202.61.71.0/24 | NTTCOM | No ROA |
| 202.61.76.0/24 | NTTCOM | No ROA |
| 202.61.77.0/24 | NTTCOM | No ROA |
| 202.61.78.0/24 | RADB | No ROA |
| 203.176.0.0/24 | NTTCOM | No ROA |
| 203.176.1.0/24 | NTTCOM | No ROA |
| 203.176.2.0/24 | NTTCOM | No ROA |
| 203.176.3.0/24 | NTTCOM | No ROA |
| 203.176.8.0/24 | NTTCOM | No ROA |
| 203.176.9.0/24 | NTTCOM | No ROA |
| 203.176.12.0/24 | NTTCOM | No ROA |
| 203.176.13.0/24 | NTTCOM | No ROA |
| 203.176.14.0/24 | NTTCOM | No ROA |
| 203.176.15.0/24 | NTTCOM | No ROA |
| 203.176.16.0/24 | NTTCOM | No ROA |
| 203.176.17.0/24 | NTTCOM | No ROA |
| 203.176.22.0/24 | NTTCOM | No ROA |
| 203.176.23.0/24 | NTTCOM | No ROA |
| 203.176.28.0/24 | NTTCOM | No ROA |
| 203.176.29.0/24 | NTTCOM | No ROA |
| 203.176.30.0/24 | NTTCOM | No ROA |
| 203.176.31.0/24 | NTTCOM | No ROA |
| 203.176.32.0/24 | NTTCOM | No ROA |
| 203.176.33.0/24 | NTTCOM | No ROA |
| 203.176.38.0/24 | NTTCOM | No ROA |
| 203.176.39.0/24 | NTTCOM | No ROA |
| 203.176.44.0/24 | NTTCOM | No ROA |
| 203.176.45.0/24 | NTTCOM | No ROA |
| 203.176.48.0/24 | NTTCOM | No ROA |
| 203.176.49.0/24 | NTTCOM | No ROA |
| 203.176.64.0/24 | NTTCOM | No ROA |
| 203.176.65.0/24 | NTTCOM | No ROA |
| 203.176.74.0/24 | NTTCOM | No ROA |
| 203.176.75.0/24 | NTTCOM | No ROA |
| 203.176.80.0/24 | NTTCOM | No ROA |
| 203.176.81.0/24 | 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.