Network · data from 2026-11-12
AS11418 LIGHTEDGE-AS-03 - LightEdge Solutions
Registry name: LIGHTEDGE-AS-03 - LightEdge Solutions, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11418, 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.
| 216.243.213.0/24 | No ROA | None | 669 99% |
| 2607:f190::/36 | No ROA | None | 635 100% |
AS-SET
AS11418 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 14 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.243.213.0/24 | No ROA covers it. Add a ROA for AS11418, maxLength 24. |
| Route object: none | 216.243.213.0/24 | No route object for it. Add a route object with origin AS11418 in the RIR database for the space. |
| ROA: none | 2607:f190::/36 | No ROA covers it. Add a ROA for AS11418, maxLength 36. |
| Route object: none | 2607:f190::/36 | No route object for it. Add a route object with origin AS11418 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11418 whose prefix no peer sees AS11418 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.71.106.0/24 | RADB | No ROA |
| 204.71.107.0/24 | RADB | No ROA |
| 205.140.160.0/24 | RADB | No ROA |
| 205.140.161.0/24 | RADB | No ROA |
| 205.140.162.0/24 | RADB | No ROA |
| 205.140.163.0/24 | RADB | No ROA |
| 206.150.144.0/24 | RADB | No ROA |
| 206.150.145.0/24 | RADB | No ROA |
| 206.150.146.0/24 | RADB | No ROA |
| 206.150.147.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.