Network · data from 2026-11-12
AS17562 DATACOM-SYSTEMS - Datacom Systems (NSW)
Registry name: DATACOM-SYSTEMS - Datacom Systems (NSW), AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17562, 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.
| 218.100.1.0/24 | No ROA | Other origin only | 671 100% |
| 167.30.144.0/24 | No ROA | None | 668 99% |
| 203.5.202.0/24 | No ROA | None | 668 99% |
| 203.5.206.0/24 | No ROA | None | 668 99% |
| 167.130.64.0/18 | No ROA | None | 664 99% |
| 167.130.81.0/24 | No ROA | None | 664 99% |
| 167.130.91.0/24 | No ROA | None | 664 99% |
| 167.130.128.0/18 | No ROA | None | 664 99% |
| 167.130.181.0/24 | No ROA | None | 664 99% |
| 167.130.191.0/24 | No ROA | None | 664 99% |
| 167.130.192.0/18 | No ROA | None | 664 99% |
AS-SET
AS17562 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 23 are in fix.csv.
- ROA: none11
- Route object: none11
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 218.100.1.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 218.100.1.0/24 | Route objects for it name AS4648, AS9328. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.30.144.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 167.30.144.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 203.5.202.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 203.5.202.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 203.5.206.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 203.5.206.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.64.0/18 | No ROA covers it. Add a ROA for AS17562, maxLength 18. |
| Route object: none | 167.130.64.0/18 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.81.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 167.130.81.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.91.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 167.130.91.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.128.0/18 | No ROA covers it. Add a ROA for AS17562, maxLength 18. |
| Route object: none | 167.130.128.0/18 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.181.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 167.130.181.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.191.0/24 | No ROA covers it. Add a ROA for AS17562, maxLength 24. |
| Route object: none | 167.130.191.0/24 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
| ROA: none | 167.130.192.0/18 | No ROA covers it. Add a ROA for AS17562, maxLength 18. |
| Route object: none | 167.130.192.0/18 | No route object for it. Add a route object with origin AS17562 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17562 whose prefix no peer sees AS17562 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.0.26.0/23 | RADB | No ROA |
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.