bgpreport

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

13IPv4 routes 23.1% RPKI valid · 15.4% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
10No ROA 13 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS394298, seen from no peer

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 2
192.234.88.128/26 Invalid: maxLength None 2 0%low visibility 2
103.228.97.0/24 No ROA Other origin only 673 100% 67
203.89.105.0/24 No ROA Other origin only 673 100% 67
170.76.177.0/24 No ROA None 670 100% 67
2620:cc:c000::/48 No ROA None 635 100% 68
2606:7a40:2::/48 No ROA None 606 95% 67
193.240.182.128/27 No ROA None 2 0%low visibility 2
170.76.176.0/29 No ROA Nonecovered by 170.76.176.0/24 1 0%low visibility 1
170.76.176.8/29 No ROA Nonecovered by 170.76.176.0/24 1 0%low visibility 1
170.76.176.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
170.76.178.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
192.234.88.0/24 Valid None 673 100% 67
203.89.104.0/24 Valid None 673 100% 67
203.89.106.0/24 Valid None 673 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: maxLength192.234.88.0/26ROA 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.2 of 673
Route object: none192.234.88.0/26No route object for it. Add a route object with origin AS394298 in the RIR database for the space.2 of 673
ROA: maxLength192.234.88.128/26ROA 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.2 of 673
Route object: none192.234.88.128/26No route object for it. Add a route object with origin AS394298 in the RIR database for the space.2 of 673
ROA: none103.228.97.0/24No ROA covers it. Add a ROA for AS394298, maxLength 24.673 of 673
Route object: none103.228.97.0/24Route objects for it name AS133428. Add a route object with origin AS394298 in the RIR database for the space.673 of 673
ROA: none203.89.105.0/24No ROA covers it. Add a ROA for AS394298, maxLength 24.673 of 673
Route object: none203.89.105.0/24Route objects for it name AS24093. Add a route object with origin AS394298 in the RIR database for the space.673 of 673
ROA: none170.76.177.0/24No ROA covers it. Add a ROA for AS394298, maxLength 24.670 of 673
Route object: none170.76.177.0/24No route object for it. Add a route object with origin AS394298 in the RIR database for the space.670 of 673
ROA: none2620:cc:c000::/48No ROA covers it. Add a ROA for AS394298, maxLength 48.635 of 636
Route object: none2620:cc:c000::/48No route object for it. Add a route object with origin AS394298 in the RIR database for the space.635 of 636
ROA: none2606:7a40:2::/48No ROA covers it. Add a ROA for AS394298, maxLength 48.606 of 636
Route object: none2606:7a40:2::/48No route object for it. Add a route object with origin AS394298 in the RIR database for the space.606 of 636
ROA: none193.240.182.128/27No ROA covers it. Add a ROA for AS394298, maxLength 27.2 of 673
Route object: none193.240.182.128/27No route object for it. Add a route object with origin AS394298 in the RIR database for the space.2 of 673
ROA: none170.76.176.0/29No ROA covers it. Add a ROA for AS394298, maxLength 29.1 of 673
Route object: none170.76.176.0/29No 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.1 of 673
ROA: none170.76.176.8/29No ROA covers it. Add a ROA for AS394298, maxLength 29.1 of 673
Route object: none170.76.176.8/29No 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.1 of 673
ROA: none170.76.176.0/24No ROA covers it. Add a ROA for AS394298, maxLength 24.670 of 673
Route object: RIR170.76.176.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.76.178.0/24No ROA covers it. Add a ROA for AS394298, maxLength 24.670 of 673
Route object: RIR170.76.178.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
Route object: none192.234.88.0/24No route object for it. Add a route object with origin AS394298 in the RIR database for the space.673 of 673
Route object: none203.89.104.0/24No route object for it. Add a route object with origin AS394298 in the RIR database for the space.673 of 673
Route object: none203.89.106.0/24No route object for it. Add a route object with origin AS394298 in the RIR database for the space.673 of 673

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/24NTTCOMNo ROA
103.228.99.0/24NTTCOMNo 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.