Network · data from 2026-11-12
AS37978 NETTAS-AS-AP - Networking Tasmania
Registry name: NETTAS-AS-AP - Networking Tasmania, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37978, 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.
| 203.18.96.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 147.41.0.0/17 | Valid | RIR databaseAPNIC | 673 100% |
| 147.41.128.0/17 | Valid | RIR databaseAPNIC | 673 100% |
| 147.41.240.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 147.109.0.0/16 | Valid | RIR databaseAPNIC | 673 100% |
| 147.109.124.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 147.109.192.0/21 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 147.109.208.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 147.109.216.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 192.26.232.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 192.107.101.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 192.190.61.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.7.8.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 203.5.121.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS37978 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.
- Route object: RIR1
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 203.18.96.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37978 whose prefix no peer sees AS37978 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 147.41.0.0/20 | APNIC | Valid |
| 147.41.16.0/20 | APNIC | Valid |
| 147.41.32.0/19 | APNIC | Valid |
| 147.41.64.0/18 | APNIC | Valid |
| 147.41.128.0/18 | APNIC | Valid |
| 147.41.192.0/19 | APNIC | Valid |
| 147.41.224.0/20 | APNIC | Valid |
| 147.109.0.0/22 | APNIC | Valid |
| 147.109.4.0/22 | APNIC | Valid |
| 147.109.8.0/21 | APNIC | Valid |
| 147.109.16.0/20 | APNIC | Valid |
| 147.109.32.0/20 | APNIC | Valid |
| 147.109.48.0/20 | APNIC | Valid |
| 147.109.64.0/20 | APNIC | Valid |
| 147.109.80.0/20 | APNIC | Valid |
| 147.109.96.0/20 | APNIC | Valid |
| 147.109.112.0/21 | APNIC | Valid |
| 147.109.120.0/22 | APNIC | Valid |
| 147.109.124.0/23 | APNIC | Valid |
| 147.109.126.0/23 | APNIC | Valid |
| 147.109.128.0/20 | APNIC | Valid |
| 147.109.144.0/20 | APNIC | Valid |
| 147.109.160.0/19 | APNIC | Valid |
| 147.109.192.0/20 | APNIC | Valid |
| 147.109.208.0/20 | APNIC, RADB | Valid |
| 147.109.224.0/20 | APNIC | Valid |
| 147.109.240.0/21 | APNIC | Valid |
| 147.109.248.0/21 | 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.