Network · data from 2026-11-12
AS46345 MTFO-01 - Luciole
Registry name: MTFO-01 - Luciole, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46345, 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.
| 66.245.224.0/20 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS46345 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 9 are in fix.csv.
- ROA: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.245.224.0/20 | No ROA covers it. Add a ROA for AS46345, maxLength 20. |
Route objects not announced
Route objects with origin AS46345 whose prefix no peer sees AS46345 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 12.70.188.0/24 | RADB | No ROA |
| 23.134.32.0/24 | ARIN | Valid |
| 23.178.0.0/24 | ARIN | Valid |
| 23.178.1.0/24 | ARIN | Valid |
| 23.252.224.0/20 | ARIN | Valid |
| 199.4.190.0/24 | ARIN | Valid |
| 2604:d040::/32 | ARIN | Valid |
| 2606:7480::/32 | ARIN | Valid |
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.