Network · data from 2026-11-12
AS394298 US-SC-DAL-AS - Airlinq Inc
Registry name: US-SC-DAL-AS - Airlinq Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394298, 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.
| 192.234.88.0/26 | Invalid: maxLength | None | 2 0%low visibility |
| 192.234.88.128/26 | Invalid: maxLength | None | 2 0%low visibility |
| 103.228.97.0/24 | No ROA | Other origin only | 673 100% |
| 203.89.105.0/24 | No ROA | Other origin only | 673 100% |
| 170.76.177.0/24 | No ROA | None | 670 100% |
| 2620:cc:c000::/48 | No ROA | None | 635 100% |
| 2606:7a40:2::/48 | No ROA | None | 606 95% |
| 193.240.182.128/27 | No ROA | None | 2 0%low visibility |
| 170.76.176.0/29 | No ROA | Nonecovered by 170.76.176.0/24 | 1 0%low visibility |
| 170.76.176.8/29 | No ROA | Nonecovered by 170.76.176.0/24 | 1 0%low visibility |
| 170.76.176.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 170.76.178.0/24 | No ROA | Other IRR onlyNTTCOM | 670 100% |
| 192.234.88.0/24 | Valid | None | 673 100% |
| 203.89.104.0/24 | Valid | None | 673 100% |
| 203.89.106.0/24 | Valid | None | 673 100% |
AS-SET
AS394298 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 29 are in fix.csv.
- ROA: maxLength2
- ROA: none10
- Route object: none13
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 192.234.88.0/26 | ROA 192.234.88.0/24 AS394298 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 192.234.88.0/26. |
| Route object: none | 192.234.88.0/26 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: maxLength | 192.234.88.128/26 | ROA 192.234.88.0/24 AS394298 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 192.234.88.128/26. |
| Route object: none | 192.234.88.128/26 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 103.228.97.0/24 | No ROA covers it. Add a ROA for AS394298, maxLength 24. |
| Route object: none | 103.228.97.0/24 | Route objects for it name AS133428. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 203.89.105.0/24 | No ROA covers it. Add a ROA for AS394298, maxLength 24. |
| Route object: none | 203.89.105.0/24 | Route objects for it name AS24093. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 170.76.177.0/24 | No ROA covers it. Add a ROA for AS394298, maxLength 24. |
| Route object: none | 170.76.177.0/24 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 2620:cc:c000::/48 | No ROA covers it. Add a ROA for AS394298, maxLength 48. |
| Route object: none | 2620:cc:c000::/48 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 2606:7a40:2::/48 | No ROA covers it. Add a ROA for AS394298, maxLength 48. |
| Route object: none | 2606:7a40:2::/48 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 193.240.182.128/27 | No ROA covers it. Add a ROA for AS394298, maxLength 27. |
| Route object: none | 193.240.182.128/27 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 170.76.176.0/29 | No ROA covers it. Add a ROA for AS394298, maxLength 29. |
| Route object: none | 170.76.176.0/29 | No route object for it. A route object for 170.76.176.0/24 with origin AS394298 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 170.76.176.8/29 | No ROA covers it. Add a ROA for AS394298, maxLength 29. |
| Route object: none | 170.76.176.8/29 | No route object for it. A route object for 170.76.176.0/24 with origin AS394298 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394298 in the RIR database for the space. |
| ROA: none | 170.76.176.0/24 | No ROA covers it. Add a ROA for AS394298, maxLength 24. |
| Route object: RIR | 170.76.176.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 170.76.178.0/24 | No ROA covers it. Add a ROA for AS394298, maxLength 24. |
| Route object: RIR | 170.76.178.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: none | 192.234.88.0/24 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| Route object: none | 203.89.104.0/24 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
| Route object: none | 203.89.106.0/24 | No route object for it. Add a route object with origin AS394298 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394298 whose prefix no peer sees AS394298 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.228.98.0/24 | NTTCOM | No ROA |
| 103.228.99.0/24 | NTTCOM | 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.