Network · data from 2026-11-12
AS37594 MTN South Sudan
Registry name: MTN South Sudan - MTN South Sudan, SS · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37594, 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.
| 102.64.73.0/24 | Valid | Nonecovered by 102.64.72.0/22 | 671 100% |
| 197.231.236.0/24 | Valid | Nonecovered by 197.231.236.0/22 | 671 100% |
| 197.231.237.0/24 | Valid | Nonecovered by 197.231.236.0/22 | 671 100% |
| 197.231.238.0/24 | Valid | Nonecovered by 197.231.236.0/22 | 671 100% |
| 197.231.239.0/24 | Valid | Nonecovered by 197.231.236.0/22 | 671 100% |
| 102.64.74.0/24 | Valid | Nonecovered by 102.64.72.0/22 | 670 100% |
| 102.64.72.0/24 | Valid | Nonecovered by 102.64.72.0/22 | 66 10%low visibility |
| 102.64.75.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 102.64.72.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 197.231.236.0/22 | Valid | RIR databaseAFRINIC | 648 96% |
AS-SET
AS37594'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 8 are in fix.csv.
- Route object: none7
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.64.73.0/24 | No route object for it. A route object for 102.64.72.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 197.231.236.0/24 | No route object for it. A route object for 197.231.236.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 197.231.237.0/24 | No route object for it. A route object for 197.231.236.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 197.231.238.0/24 | No route object for it. A route object for 197.231.236.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 197.231.239.0/24 | No route object for it. A route object for 197.231.236.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 102.64.74.0/24 | No route object for it. A route object for 102.64.72.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: none | 102.64.72.0/24 | No route object for it. A route object for 102.64.72.0/22 with origin AS37594 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37594 in the RIR database for the space. |
| Route object: RIR | 102.64.75.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS37594 is announced.
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.