Network · data from 2026-11-12
AS38561 NTT Australian Domestic Peering Network
Registry name: DOM-AU-AP - NTT Australia Solutions Pty Ltd, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38561, 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.67.236.0/24 | Valid | Nonecovered by 192.67.236.0/22 | 99 15% |
| 192.67.237.0/24 | Valid | Nonecovered by 192.67.236.0/22 | 99 15% |
| 192.67.238.0/24 | Valid | Nonecovered by 192.67.236.0/22 | 99 15% |
| 192.67.239.0/24 | Valid | Nonecovered by 192.67.236.0/22 | 99 15% |
| 192.67.236.0/22 | Valid | Other IRR onlyNTTCOM | 99 15% |
| 2402:f00::/32 | Valid | RIR databaseAPNIC, RADB | 235 37% |
| 202.9.114.0/23 | Valid | RIR databaseAPNIC | 95 14% |
| 202.9.112.0/23 | Valid | RIR databaseAPNIC | 70 10% |
| 202.9.112.0/22 | Valid | RIR databaseAPNIC | 29 4%low visibility |
AS-SET
PeeringDB's irr_as_set for AS38561: AS38561:AS-AU. 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 (AS38561 isn't in the set, or no route object for AS38561 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 | AS38561 in it | Not covered |
|---|---|---|---|---|---|
| AS38561:AS-AU | NTTCOM | 31 | 2 | Yes | 0 |
| APNIC (also)1 member set in no database: AS-NTTGN-AP | 35 | 2 | Yes | 0 |
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 9 are in fix.csv.
- Route object: none4
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 192.67.236.0/24 | No route object for it. A route object for 192.67.236.0/22 with origin AS38561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38561 in the RIR database for the space. |
| Route object: none | 192.67.237.0/24 | No route object for it. A route object for 192.67.236.0/22 with origin AS38561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38561 in the RIR database for the space. |
| Route object: none | 192.67.238.0/24 | No route object for it. A route object for 192.67.236.0/22 with origin AS38561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38561 in the RIR database for the space. |
| Route object: none | 192.67.239.0/24 | No route object for it. A route object for 192.67.236.0/22 with origin AS38561 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38561 in the RIR database for the space. |
| Route object: RIR | 192.67.236.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38561 whose prefix no peer sees AS38561 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.9.112.0/24 | APNIC | Valid |
| 202.9.113.0/24 | APNIC | Valid |
| 202.9.114.0/24 | APNIC | Valid |
| 202.9.115.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.