Network · data from 2026-11-12
AS56068 LIGHTSPEED-TECHNOLOGY-AS-AP - Lightspeed Technology Group Limited
Registry name: LIGHTSPEED-TECHNOLOGY-AS-AP - Lightspeed Technology Group Limited, NZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56068, 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.
| 206.62.34.0/23 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.37.204.0/22 | No ROA | RIR databaseAPNIC | 671 100% |
| 202.49.80.0/23 | No ROA | RIR databaseAPNIC | 671 100% |
| 2001:df0:f6::/48 | No ROA | RIR databaseAPNIC | 635 100% |
| 2402:1f20::/32 | No ROA | RIR databaseAPNIC | 635 100% |
AS-SET
AS56068 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 11 are in fix.csv.
- ROA: none5
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 206.62.34.0/23 | No ROA covers it. Add a ROA for AS56068, maxLength 23. |
| Route object: RIR | 206.62.34.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.37.204.0/22 | No ROA covers it. Add a ROA for AS56068, maxLength 22. |
| ROA: none | 202.49.80.0/23 | No ROA covers it. Add a ROA for AS56068, maxLength 23. |
| ROA: none | 2001:df0:f6::/48 | No ROA covers it. Add a ROA for AS56068, maxLength 48. |
| ROA: none | 2402:1f20::/32 | No ROA covers it. Add a ROA for AS56068, maxLength 32. |
Route objects not announced
Route objects with origin AS56068 whose prefix no peer sees AS56068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.203.76.0/23 | APNIC | Valid |
| 131.203.76.0/24 | APNIC | Valid |
| 131.203.77.0/24 | APNIC | Valid |
| 202.49.80.0/24 | APNIC, RADB | No ROA |
| 202.49.81.0/24 | 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.