Network · data from 2026-11-12
AS132825 Defense Australia Network
Registry name: MYTEK-AS-AP - MYTEK TRADING PTY LTD, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132825, 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.
| 2402:5c60::/32 | No ROA | None | 319 50% |
| 154.6.164.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 45.204.21.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
| 2407:1100::/32 | No ROA | Other IRR onlyRADB | 636 100% |
| 2407:1100::/36 | No ROA | Other IRR onlyRADB | 632 99% |
| 2407:1100:1000::/36 | No ROA | Other IRR onlyRADB | 631 99% |
| 119.42.35.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 43.251.113.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 43.251.115.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.125.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.125.85.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.125.86.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.125.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 118.107.192.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 118.107.246.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 118.107.252.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 119.42.32.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 43.230.10.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 43.230.11.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 43.231.4.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 43.231.5.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.231.6.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.231.7.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 43.252.208.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.228.65.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.234.52.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.234.55.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.239.100.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.239.101.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.250.4.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.250.6.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.107.193.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.194.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.244.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.245.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.247.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.248.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.253.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.107.254.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.5.70.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 181.215.252.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.135.72.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 185.135.73.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 185.135.75.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 185.135.76.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 43.249.252.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.251.112.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 118.107.250.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 118.107.251.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 118.107.255.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 154.93.24.0/23 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 185.135.78.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 185.135.79.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 43.251.114.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.250.7.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 118.107.195.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 118.107.249.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 119.42.34.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 185.135.74.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 185.135.77.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.250.5.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 2402:5c60::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:5c60:1000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2402:5c60:2000::/36 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df0:fbc0::/48 | Valid | RIR databaseAPNIC, RADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS132825: RADB::AS-GIGADEFENCE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132825 isn't in the set, or no route object for AS132825 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS132825 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-GIGADEFENCE | RADB | 27 | 1 | Yes | 1 |
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 73 are in fix.csv.
- ROA: none6
- Route object: none1
- Route object: RIR6
- Route object: not announced60
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2402:5c60::/32 | No ROA covers it. Add a ROA for AS132825, maxLength 32. |
| Route object: none | 2402:5c60::/32 | No route object for it. Add a route object with origin AS132825 in the RIR database for the space. |
| ROA: none | 154.6.164.0/24 | No ROA covers it. Add a ROA for AS132825, maxLength 24. |
| Route object: RIR | 154.6.164.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.204.21.0/24 | No ROA covers it. Add a ROA for AS132825, maxLength 24. |
| Route object: RIR | 45.204.21.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2407:1100::/32 | No ROA covers it. Add a ROA for AS132825, maxLength 32. |
| Route object: RIR | 2407:1100::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2407:1100::/36 | No ROA covers it. Add a ROA for AS132825, maxLength 36. |
| Route object: RIR | 2407:1100::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2407:1100:1000::/36 | No ROA covers it. Add a ROA for AS132825, maxLength 36. |
| Route object: RIR | 2407:1100:1000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.42.35.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132825 whose prefix no peer sees AS132825 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.249.253.0/24 | APNIC | Valid |
| 43.251.112.0/22 | RADB | No ROA |
| 103.99.40.0/23 | APNIC | Valid |
| 103.99.40.0/24 | APNIC | Valid |
| 103.99.41.0/24 | APNIC | Valid |
| 103.113.92.0/22 | APNIC | Valid |
| 103.113.92.0/23 | APNIC | Valid |
| 103.113.92.0/24 | APNIC | Valid |
| 103.113.93.0/24 | APNIC | Valid |
| 103.113.94.0/23 | APNIC | Valid |
| 103.113.94.0/24 | APNIC | Valid |
| 103.113.95.0/24 | APNIC | Valid |
| 103.125.84.0/22 | RADB | No ROA |
| 103.132.234.0/23 | APNIC | Valid |
| 103.132.234.0/24 | APNIC | Valid |
| 103.132.235.0/24 | APNIC | Valid |
| 103.133.176.0/22 | APNIC | Valid |
| 103.133.176.0/23 | APNIC | Valid |
| 103.133.176.0/24 | APNIC | Valid |
| 103.133.177.0/24 | APNIC | Valid |
| 103.133.178.0/23 | APNIC | Valid |
| 103.133.178.0/24 | APNIC | Valid |
| 103.133.179.0/24 | APNIC | Valid |
| 103.140.228.0/23 | APNIC | Valid |
| 103.140.228.0/24 | APNIC | Valid |
| 103.140.229.0/24 | APNIC | Valid |
| 103.145.38.0/23 | APNIC | Valid |
| 103.145.38.0/24 | APNIC | Valid |
| 103.145.39.0/24 | APNIC | Valid |
| 103.150.181.0/24 | APNIC | Valid |
| 103.151.216.0/23 | APNIC | Valid |
| 103.151.216.0/24 | APNIC | Valid |
| 103.151.217.0/24 | APNIC | Valid |
| 103.152.170.0/23 | APNIC | Valid |
| 103.152.170.0/24 | APNIC | Valid |
| 103.152.171.0/24 | APNIC | Valid |
| 103.153.36.0/23 | APNIC | Valid |
| 103.153.36.0/24 | APNIC | Valid |
| 103.153.37.0/24 | APNIC | Valid |
| 103.153.100.0/23 | APNIC | Valid |
| 103.153.100.0/24 | APNIC | Valid |
| 103.153.101.0/24 | APNIC | Valid |
| 103.153.138.0/23 | APNIC | Valid |
| 103.153.138.0/24 | APNIC | Valid |
| 103.153.139.0/24 | APNIC | Valid |
| 103.155.110.0/23 | APNIC | Valid |
| 103.155.110.0/24 | APNIC | Valid |
| 103.155.111.0/24 | APNIC | Valid |
| 103.229.64.0/22 | RADB | No ROA |
| 103.230.192.0/22 | RADB | No ROA |
| 103.250.4.0/22 | RADB | No ROA |
| 119.42.32.0/22 | RADB | No ROA |
| 220.158.200.0/23 | RADB | No ROA |
| 2402:5c60:3000::/36 | APNIC | Valid |
| 2402:5c60:4000::/36 | APNIC | Valid |
| 2402:5c60:5000::/36 | APNIC | Valid |
| 2402:5c60:6000::/36 | APNIC | Valid |
| 2402:5c60:7000::/36 | APNIC | Valid |
| 2402:5c60:8000::/36 | APNIC | Valid |
| 2402:5c60:9000::/36 | 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.