Network · data from 2026-11-12
AS40498 ABQG - New Mexico Lambda Rail, Inc.
Registry name: ABQG - New Mexico Lambda Rail, Inc., US · not in PeeringDB
19IPv4 routes
0.0% RPKI valid · 68.4% with a route object
2IPv6 routes
0.0% RPKI valid · 50.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
21No ROA
7 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
15Route objects not announced
registered with origin AS40498, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS40498, 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.
| 64.106.82.0/24 | No ROA | Nonecovered by 64.106.80.0/20 | 1 0%low visibility |
| 64.106.83.0/24 | No ROA | Nonecovered by 64.106.80.0/20 | 1 0%low visibility |
| 129.24.212.0/24 | No ROA | None | 1 0%low visibility |
| 129.24.213.0/24 | No ROA | None | 1 0%low visibility |
| 137.164.50.192/30 | No ROA | None | 1 0%low visibility |
| 208.77.78.172/30 | No ROA | Nonecovered by 208.77.76.0/22 | 1 0%low visibility |
| 2607:f380:1::118:9a43:2c00/122 | No ROA | None | 1 0%low visibility |
| 204.134.67.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 204.134.68.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.136.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.137.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.138.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.139.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.140.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.141.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.142.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.206.143.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.77.76.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 198.59.97.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2001:48e0::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 64.106.80.0/20 | No ROA | Other IRR onlyRADB | 1 0%low visibility |
AS-SET
AS40498 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 57 are in fix.csv.
- ROA: none21
- Route object: none7
- Route object: RIR14
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.106.82.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: none | 64.106.82.0/24 | No route object for it. A route object for 64.106.80.0/20 with origin AS40498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 64.106.83.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: none | 64.106.83.0/24 | No route object for it. A route object for 64.106.80.0/20 with origin AS40498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 129.24.212.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: none | 129.24.212.0/24 | No route object for it. Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 129.24.213.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: none | 129.24.213.0/24 | No route object for it. Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 137.164.50.192/30 | No ROA covers it. Add a ROA for AS40498, maxLength 30. |
| Route object: none | 137.164.50.192/30 | No route object for it. Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 208.77.78.172/30 | No ROA covers it. Add a ROA for AS40498, maxLength 30. |
| Route object: none | 208.77.78.172/30 | No route object for it. A route object for 208.77.76.0/22 with origin AS40498 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 2607:f380:1::118:9a43:2c00/122 | No ROA covers it. Add a ROA for AS40498, maxLength 122. |
| Route object: none | 2607:f380:1::118:9a43:2c00/122 | No route object for it. Add a route object with origin AS40498 in the RIR database for the space. |
| ROA: none | 204.134.67.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 204.134.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 204.134.68.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 204.134.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.136.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.136.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.137.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.138.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.138.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.139.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.139.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.140.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.140.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.141.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.142.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.142.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.206.143.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 206.206.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.77.76.0/22 | No ROA covers it. Add a ROA for AS40498, maxLength 22. |
| Route object: RIR | 208.77.76.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.59.97.0/24 | No ROA covers it. Add a ROA for AS40498, maxLength 24. |
| Route object: RIR | 198.59.97.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:48e0::/32 | No ROA covers it. Add a ROA for AS40498, maxLength 32. |
| Route object: RIR | 2001:48e0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.106.80.0/20 | No ROA covers it. Add a ROA for AS40498, maxLength 20. |
| Route object: RIR | 64.106.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40498 whose prefix no peer sees AS40498 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.132.89.0/24 | RADB | No ROA |
| 198.51.249.0/24 | RADB | No ROA |
| 198.59.106.0/24 | RADB | No ROA |
| 198.59.107.0/24 | RADB | No ROA |
| 198.59.108.0/24 | RADB | No ROA |
| 198.59.132.0/24 | RADB | No ROA |
| 198.59.169.0/24 | RADB | No ROA |
| 198.59.188.0/24 | RADB | No ROA |
| 198.59.189.0/24 | RADB | No ROA |
| 198.59.190.0/24 | RADB | No ROA |
| 205.166.231.0/24 | RADB | No ROA |
| 206.206.136.0/21 | RADB | No ROA |
| 207.108.245.224/27 | RADB | No ROA |
| 216.161.32.0/23 | RADB | No ROA |
| 216.184.0.0/19 | 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.