Network · data from 2026-11-12
AS214358 MTEL-CH-AS MTEL Schweiz GmbH
Registry name: MTEL-CH-AS MTEL Schweiz GmbH, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214358, 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.
| 109.121.112.0/23 | Valid | Nonecovered by 109.121.112.0/22 | 673 100% |
| 109.121.114.0/24 | Valid | Nonecovered by 109.121.112.0/22 | 673 100% |
| 109.121.115.0/24 | Valid | Nonecovered by 109.121.112.0/22 | 673 100% |
| 2001:3b00:200::/40 | Valid | Nonecovered by 2001:3b00::/29 | 635 100% |
| 2001:3b00:300::/40 | Valid | Nonecovered by 2001:3b00::/29 | 635 100% |
| 2001:3b00:400::/40 | Valid | Nonecovered by 2001:3b00::/29 | 635 100% |
AS-SET
AS214358 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 9 are in fix.csv.
- Route object: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.121.112.0/23 | No route object for it. A route object for 109.121.112.0/22 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
| Route object: none | 109.121.114.0/24 | No route object for it. A route object for 109.121.112.0/22 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
| Route object: none | 109.121.115.0/24 | No route object for it. A route object for 109.121.112.0/22 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
| Route object: none | 2001:3b00:200::/40 | No route object for it. A route object for 2001:3b00::/29 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
| Route object: none | 2001:3b00:300::/40 | No route object for it. A route object for 2001:3b00::/29 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
| Route object: none | 2001:3b00:400::/40 | No route object for it. A route object for 2001:3b00::/29 with origin AS214358 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214358 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214358 whose prefix no peer sees AS214358 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.121.112.0/22 | RIPE | No ROA |
| 185.166.93.0/24 | RIPE | Valid |
| 2001:3b00::/29 | 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.