Network · data from 2026-11-12
AS329024 LULI FIBRA CABLE SOLUTION
Registry name: LULI FIBRA CABLE SOLUTION LIMITED - LULI FIBRA CABLE SOLUTION LIMITED, NG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS329024, 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.
| 102.216.180.0/22 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 102.216.180.0/23 | No ROA | Other IRR onlyALTDB, RADB | 671 100% |
| 102.216.182.0/23 | No ROA | Other IRR onlyALTDB | 671 100% |
| 2c0f:480::/32 | No ROA | Other IRR onlyALTDB | 635 100% |
| 102.216.180.0/24 | No ROA | Other IRR onlyALTDB, RADB | 2 0%low visibility |
| 102.216.181.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
| 102.216.182.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
| 102.216.183.0/24 | No ROA | Other IRR onlyALTDB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS329024: AS-329024. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS329024 isn't in the set, or no route object for AS329024 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS329024 in it | Not covered |
|---|---|---|---|---|---|
| AS-329024 | ALTDB1 member set in no database: AS329024:AS-CUSTOMERS | 1 | 1 | Yes | 0 |
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 17 are in fix.csv.
- ROA: none8
- Route object: RIR8
- AS-SET: missing member1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.216.180.0/22 | No ROA covers it. Add a ROA for AS329024, maxLength 22. |
| Route object: RIR | 102.216.180.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 102.216.180.0/23 | No ROA covers it. Add a ROA for AS329024, maxLength 23. |
| Route object: RIR | 102.216.180.0/23 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 102.216.182.0/23 | No ROA covers it. Add a ROA for AS329024, maxLength 23. |
| Route object: RIR | 102.216.182.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2c0f:480::/32 | No ROA covers it. Add a ROA for AS329024, maxLength 32. |
| Route object: RIR | 2c0f:480::/32 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 102.216.180.0/24 | No ROA covers it. Add a ROA for AS329024, maxLength 24. |
| Route object: RIR | 102.216.180.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 102.216.181.0/24 | No ROA covers it. Add a ROA for AS329024, maxLength 24. |
| Route object: RIR | 102.216.181.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 102.216.182.0/24 | No ROA covers it. Add a ROA for AS329024, maxLength 24. |
| Route object: RIR | 102.216.182.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 102.216.183.0/24 | No ROA covers it. Add a ROA for AS329024, maxLength 24. |
| Route object: RIR | 102.216.183.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-329024 | AS-329024 (ALTDB) lists AS329024:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS329024 is announced.
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.