Network · data from 2026-11-12
AS149841 LIGHTNING1-AS-AP - Lightning IP
Registry name: LIGHTNING1-AS-AP - Lightning IP, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149841, 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.
| 38.211.250.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.224.62.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.187.240.0/23 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2400:7fa0::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
AS149841 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 4 are in fix.csv.
- ROA: none2
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.211.250.0/24 | No ROA covers it. Add a ROA for AS149841, maxLength 24. |
| Route object: RIR | 38.211.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.224.62.0/24 | No ROA covers it. Add a ROA for AS149841, maxLength 24. |
| Route object: RIR | 38.224.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS149841 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.