Network · data from 2026-11-12
AS18345 SERVERS-AUS-CUST - Servers Australia Customers
Registry name: SERVERS-AUS-CUST - Servers Australia Customers, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18345, 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.
| 181.214.215.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 181.214.51.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 178.157.93.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 181.214.23.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 181.214.104.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 185.164.123.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 191.101.211.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS18345 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 11 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 181.214.215.0/24 | No ROA covers it. Add a ROA for AS18345, maxLength 24. |
| Route object: RIR | 181.214.215.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 AS18345 whose prefix no peer sees AS18345 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.199.27.0/24 | RIPE | Invalid: origin |
| 154.16.81.0/24 | AFRINIC | Invalid: origin |
| 156.6.151.0/24 | RADB | No ROA |
| 173.239.194.0/24 | NTTCOM, RADB | Valid |
| 173.239.203.0/24 | NTTCOM, RADB | Valid |
| 191.96.214.0/24 | RIPE | Invalid: origin |
| 202.60.80.0/24 | RADB | Valid |
| 202.60.81.0/24 | APNIC | Valid |
| 202.60.82.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.