Network · data from 2026-11-12
AS9301 Multiline AS9301
Registry name: EWN-AS-AP - Cynergic, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9301, 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.
| 122.200.171.0/24 | No ROA | Other origin only | 672 100% |
| 163.223.196.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.56.99.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 122.200.164.0/24 | Valid | None | 672 100% |
| 122.200.165.0/24 | Valid | None | 672 100% |
| 122.200.168.0/24 | Valid | None | 672 100% |
| 122.200.173.0/24 | Valid | None | 672 100% |
| 203.4.162.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.5.127.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.31.57.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.31.101.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS9301: AS9301:AS-MULTILINEAU. 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 (AS9301 isn't in the set, or no route object for AS9301 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 | AS9301 in it | Not covered |
|---|---|---|---|---|---|
| AS9301:AS-MULTILINEAU | APNIC | 4 | 1 | Yes | 5 |
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 12 are in fix.csv.
- ROA: none3
- Route object: none5
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 122.200.171.0/24 | No ROA covers it. Add a ROA for AS9301, maxLength 24. |
| Route object: none | 122.200.171.0/24 | Route objects for it name AS24093. Add a route object with origin AS9301 in the RIR database for the space. |
| ROA: none | 163.223.196.0/23 | No ROA covers it. Add a ROA for AS9301, maxLength 23. |
| ROA: none | 203.56.99.0/24 | No ROA covers it. Add a ROA for AS9301, maxLength 24. |
| Route object: none | 122.200.164.0/24 | No route object for it. Add a route object with origin AS9301 in the RIR database for the space. |
| Route object: none | 122.200.165.0/24 | No route object for it. Add a route object with origin AS9301 in the RIR database for the space. |
| Route object: none | 122.200.168.0/24 | No route object for it. Add a route object with origin AS9301 in the RIR database for the space. |
| Route object: none | 122.200.173.0/24 | No route object for it. Add a route object with origin AS9301 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9301 whose prefix no peer sees AS9301 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.33.71.0/24 | APNIC | Valid |
| 203.56.14.0/24 | RADB | No ROA |
| 203.56.15.0/24 | RADB | No ROA |
| 203.57.79.0/24 | 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.