Network · data from 2026-11-12
AS8247 Calltrade-Zurich Intellico AG
Registry name: Calltrade-Zurich Intellico AG, CH · not in PeeringDB
20IPv4 routes
100.0% RPKI valid · 25.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
15 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS8247, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS8247, 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.
| 213.232.150.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.160.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.161.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.162.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.163.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.172.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.173.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.174.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.175.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.180.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.181.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.182.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.183.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.190.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.191.0/24 | Valid | Nonecovered by 213.232.128.0/18 | 673 100% |
| 213.232.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.232.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.232.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.232.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.232.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS8247 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 33 are in fix.csv.
- Route object: none15
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 213.232.150.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.160.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.161.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.162.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.163.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.172.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.173.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.174.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.175.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.180.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.181.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.182.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.183.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.190.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
| Route object: none | 213.232.191.0/24 | No route object for it. A route object for 213.232.128.0/18 with origin AS8247 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8247 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8247 whose prefix no peer sees AS8247 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.227.101.0/24 | RIPE | No ROA |
| 195.200.218.0/24 | RIPE | No ROA |
| 213.232.128.0/18 | RIPE | No ROA |
| 213.232.129.0/24 | RIPE | No ROA |
| 213.232.130.0/24 | RIPE | No ROA |
| 213.232.136.0/24 | RIPE | No ROA |
| 213.232.137.0/24 | RIPE | No ROA |
| 213.232.138.0/24 | RIPE | No ROA |
| 213.232.139.0/24 | RIPE | No ROA |
| 213.232.140.0/24 | RIPE | No ROA |
| 213.232.141.0/24 | RIPE | No ROA |
| 213.232.142.0/24 | RIPE | No ROA |
| 213.232.143.0/24 | RIPE | No ROA |
| 213.232.144.0/24 | RIPE | No ROA |
| 213.232.145.0/24 | RIPE | No ROA |
| 213.232.146.0/24 | RIPE | No ROA |
| 213.232.147.0/24 | RIPE | No ROA |
| 213.232.148.0/24 | RIPE | 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.