Network · data from 2026-11-12
AS135348 QANTASAIRLTD-AS-AP - QANTAS Airways Limited
Registry name: QANTASAIRLTD-AS-AP - QANTAS Airways Limited, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135348, 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.
| 139.163.0.0/16 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 168.134.0.0/16 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 139.163.30.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 139.163.131.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 139.163.132.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 139.163.138.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 139.163.250.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 168.134.136.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 139.163.247.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 168.134.137.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS135348 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: none2
- Route object: RIR2
- Route object: not announced25
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 139.163.0.0/16 | No ROA covers it. Add a ROA for AS135348, maxLength 16. |
| Route object: RIR | 139.163.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 168.134.0.0/16 | No ROA covers it. Add a ROA for AS135348, maxLength 16. |
| Route object: RIR | 168.134.0.0/16 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135348 whose prefix no peer sees AS135348 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.163.0.0/17 | APNIC, RADB | Valid |
| 139.163.128.0/17 | RADB | No ROA |
| 139.163.128.0/23 | APNIC | Valid |
| 139.163.130.0/24 | APNIC | Valid |
| 139.163.132.0/22 | APNIC | Valid |
| 139.163.136.0/23 | APNIC | Valid |
| 139.163.139.0/24 | APNIC | Valid |
| 139.163.140.0/22 | APNIC | Valid |
| 139.163.144.0/20 | APNIC | Valid |
| 139.163.160.0/19 | APNIC | Valid |
| 139.163.192.0/19 | APNIC | Valid |
| 139.163.224.0/20 | APNIC | Valid |
| 139.163.240.0/22 | APNIC | Valid |
| 139.163.244.0/23 | APNIC | Valid |
| 139.163.246.0/24 | APNIC | Valid |
| 139.163.248.0/21 | APNIC | Valid |
| 168.134.0.0/17 | APNIC, RADB | Valid |
| 168.134.128.0/17 | RADB | No ROA |
| 168.134.128.0/21 | APNIC | Valid |
| 168.134.138.0/24 | APNIC | Valid |
| 168.134.139.0/24 | APNIC | Valid |
| 168.134.140.0/22 | APNIC | Valid |
| 168.134.144.0/20 | APNIC | Valid |
| 168.134.160.0/19 | APNIC | Valid |
| 168.134.192.0/18 | APNIC | Valid |
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.