Network · data from 2026-11-12
AS36939 Comores Telecom
Registry name: Comores Telecom - Comores Telecom, KM · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36939, 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.
| 197.255.224.0/21 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.224.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.225.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.226.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.227.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.228.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.229.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.230.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.231.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.232.0/21 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.236.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.238.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 197.255.239.0/24 | Valid | Nonecovered by 197.255.224.0/20 | 673 100% |
| 2c0f:f560::/32 | Valid | RIR databaseAFRINIC | 636 100% |
AS-SET
AS36939's PeeringDB record names no 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 14 are in fix.csv.
- Route object: none13
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 197.255.224.0/21 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.224.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.225.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.226.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.227.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.228.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.229.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.230.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.231.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.232.0/21 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.236.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.238.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
| Route object: none | 197.255.239.0/24 | No route object for it. A route object for 197.255.224.0/20 with origin AS36939 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36939 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36939 whose prefix no peer sees AS36939 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 197.255.224.0/20 | AFRINIC, RIPE-NONAUTH | Valid |
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.