Network · data from 2026-11-12
AS327850 XON Systems (Pty) Ltd
Registry name: NEC XON SYSTEMS (PTY) LTD - NEC XON SYSTEMS (PTY) LTD, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS327850, 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.
| 196.223.192.0/20 | No ROA | Nonecovered by 196.223.192.0/19 | 673 100% |
| 168.253.216.0/21 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 168.253.218.0/24 | No ROA | RIR databaseAFRINIC | 673 100% |
| 196.223.192.0/19 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.223.192.0/24 | No ROA | RIR databaseAFRINIC | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS327850: AS-XON. 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 (AS327850 isn't in the set, or no route object for AS327850 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 | AS327850 in it | Not covered |
|---|---|---|---|---|---|
| AS-XON | AFRINIC | 1 | 1 | Yes | 0 |
| RIPE (also) | 2 | 1 | No | 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 23 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.223.192.0/20 | No ROA covers it. Add a ROA for AS327850, maxLength 20. |
| Route object: none | 196.223.192.0/20 | No route object for it. A route object for 196.223.192.0/19 with origin AS327850 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327850 in the RIR database for the space. |
| ROA: none | 168.253.216.0/21 | No ROA covers it. Add a ROA for AS327850, maxLength 21. |
| ROA: none | 168.253.218.0/24 | No ROA covers it. Add a ROA for AS327850, maxLength 24. |
| ROA: none | 196.223.192.0/19 | No ROA covers it. Add a ROA for AS327850, maxLength 19. |
| ROA: none | 196.223.192.0/24 | No ROA covers it. Add a ROA for AS327850, maxLength 24. |
Route objects not announced
Route objects with origin AS327850 whose prefix no peer sees AS327850 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.253.216.0/24 | AFRINIC | No ROA |
| 168.253.217.0/24 | AFRINIC | No ROA |
| 168.253.219.0/24 | AFRINIC | No ROA |
| 168.253.220.0/24 | AFRINIC | No ROA |
| 168.253.221.0/24 | AFRINIC | No ROA |
| 168.253.222.0/24 | AFRINIC | No ROA |
| 168.253.223.0/24 | AFRINIC | No ROA |
| 196.223.192.0/23 | AFRINIC | No ROA |
| 196.223.193.0/24 | AFRINIC | No ROA |
| 196.223.194.0/23 | AFRINIC | No ROA |
| 196.223.196.0/23 | AFRINIC | No ROA |
| 196.223.198.0/23 | AFRINIC | No ROA |
| 196.223.200.0/23 | AFRINIC | No ROA |
| 196.223.202.0/23 | AFRINIC | No ROA |
| 196.223.204.0/23 | AFRINIC | No ROA |
| 196.223.206.0/23 | AFRINIC | No ROA |
| 196.223.208.0/20 | AFRINIC | 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.