Network · data from 2026-11-12
AS43378 MoCISA Ministry of Commerce and Industry in Saudi Arabia
Registry name: MoCISA Ministry of Commerce and Industry in Saudi Arabia, SA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43378, 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.248.249.160/28 | Invalid: origin | None | 1 0%low visibility |
| 91.221.184.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 91.221.185.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 91.221.184.0/23 | No ROA | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS43378 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 5 are in fix.csv.
- ROA: origin1
- ROA: none3
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 188.248.249.160/28 | ROAs covering it name AS19905, AS47794, AS48695, not AS43378. If AS43378 should announce it, add a ROA for AS43378. |
| Route object: none | 188.248.249.160/28 | No route object for it. Add a route object with origin AS43378 in the RIR database for the space. |
| ROA: none | 91.221.184.0/24 | No ROA covers it. Add a ROA for AS43378, maxLength 24. |
| ROA: none | 91.221.185.0/24 | No ROA covers it. Add a ROA for AS43378, maxLength 24. |
| ROA: none | 91.221.184.0/23 | No ROA covers it. Add a ROA for AS43378, maxLength 23. |
Route objects not announced
Every route object with origin AS43378 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.