Network · data from 2026-11-12
AS16818 SYNTAX-NJ-AZ - Syntax systems Ltd LLC.
Registry name: SYNTAX-NJ-AZ - Syntax systems Ltd LLC., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16818, 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.
| 153.95.224.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 153.95.226.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 204.8.104.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 204.8.106.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 204.8.107.0/24 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS16818 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 7 are in fix.csv.
- ROA: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 153.95.224.0/23 | No ROA covers it. Add a ROA for AS16818, maxLength 23. |
| ROA: none | 153.95.226.0/23 | No ROA covers it. Add a ROA for AS16818, maxLength 23. |
| ROA: none | 204.8.104.0/23 | No ROA covers it. Add a ROA for AS16818, maxLength 23. |
| ROA: none | 204.8.106.0/24 | No ROA covers it. Add a ROA for AS16818, maxLength 24. |
| ROA: none | 204.8.107.0/24 | No ROA covers it. Add a ROA for AS16818, maxLength 24. |
Route objects not announced
Route objects with origin AS16818 whose prefix no peer sees AS16818 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 204.8.104.0/22 | RADB | No ROA |
| 208.168.207.0/24 | 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.