Network · data from 2026-11-12
AS54963 LUMENET - Lume Technologies Inc.
Registry name: LUMENET - Lume Technologies Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54963, 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.214.106.0/23 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 192.214.110.0/23 | Valid | RIR databaseARIN, RADB | 673 100% |
| 192.214.111.0/24 | Valid | RIR databaseARIN | 673 100% |
| 144.168.35.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS54963 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 10 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.214.106.0/23 | No ROA covers it. Add a ROA for AS54963, maxLength 23. |
| Route object: RIR | 192.214.106.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54963 whose prefix no peer sees AS54963 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 144.168.33.0/24 | ARIN | Valid |
| 192.214.104.0/24 | ARIN | No ROA |
| 192.214.105.0/24 | ARIN | No ROA |
| 192.214.106.0/24 | ARIN | No ROA |
| 192.214.107.0/24 | ARIN | No ROA |
| 192.214.108.0/24 | ARIN | No ROA |
| 192.214.109.0/24 | ARIN | Invalid: origin |
| 192.214.110.0/24 | 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.