Network · data from 2026-11-12
AS200729 MCIT AzInTelecom LLC
Registry name: MCIT AzInTelecom LLC, AZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200729, 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.
| 188.72.138.0/24 | No ROA | Other origin onlycovered by 188.72.128.0/20 | 673 100% |
| 188.72.133.0/24 | No ROA | Other origin onlycovered by 188.72.128.0/20 | 3 0%low visibility |
| 188.72.134.0/24 | No ROA | Other origin onlycovered by 188.72.128.0/20 | 3 0%low visibility |
| 188.72.128.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 188.72.128.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 188.72.189.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 5.191.251.0/24 | Valid | Nonecovered by 5.191.240.0/20 | 673 100% |
| 5.191.252.0/23 | Valid | Nonecovered by 5.191.240.0/20 | 673 100% |
| 185.96.124.0/24 | Valid | Nonecovered by 185.96.124.0/22 | 672 100% |
| 5.191.242.0/24 | Valid | Nonecovered by 5.191.240.0/20 | 1 0%low visibility |
| 185.96.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.191.240.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 85.132.83.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.20.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.96.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.96.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.143.196.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.143.197.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.143.198.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.143.199.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS200729 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 24 are in fix.csv.
- ROA: none6
- Route object: none7
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.72.138.0/24 | No ROA covers it. Add a ROA for AS200729, maxLength 24. |
| Route object: none | 188.72.138.0/24 | Route objects for it name AS196821. A route object for 188.72.128.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| ROA: none | 188.72.133.0/24 | No ROA covers it. Add a ROA for AS200729, maxLength 24. |
| Route object: none | 188.72.133.0/24 | Route objects for it name AS196821. A route object for 188.72.128.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| ROA: none | 188.72.134.0/24 | No ROA covers it. Add a ROA for AS200729, maxLength 24. |
| Route object: none | 188.72.134.0/24 | Route objects for it name AS196821. A route object for 188.72.128.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| ROA: none | 188.72.128.0/18 | No ROA covers it. Add a ROA for AS200729, maxLength 18. |
| ROA: none | 188.72.128.0/24 | No ROA covers it. Add a ROA for AS200729, maxLength 24. |
| ROA: none | 188.72.189.0/24 | No ROA covers it. Add a ROA for AS200729, maxLength 24. |
| Route object: none | 5.191.251.0/24 | No route object for it. A route object for 5.191.240.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| Route object: none | 5.191.252.0/23 | No route object for it. A route object for 5.191.240.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| Route object: none | 185.96.124.0/24 | No route object for it. A route object for 185.96.124.0/22 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
| Route object: none | 5.191.242.0/24 | No route object for it. A route object for 5.191.240.0/20 with origin AS200729 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200729 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200729 whose prefix no peer sees AS200729 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.96.124.0/22 | RIPE | No ROA |
| 185.143.196.0/24 | RIPE | Valid |
| 188.72.128.0/20 | RIPE | No ROA |
| 188.72.144.0/21 | RIPE | No ROA |
| 188.72.150.0/24 | RIPE | No ROA |
| 188.72.168.0/21 | RIPE | No ROA |
| 188.72.176.0/20 | RIPE | No ROA |
| 188.72.184.0/24 | RIPE | No ROA |
| 188.72.185.0/24 | RIPE | No ROA |
| 188.72.186.0/24 | RIPE | No ROA |
| 188.72.187.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.