bgpreport

Network · data from 2026-11-12

AS198795 NIC-SAIX-P-Cloud NIC (National Information Center)- SDAIA ( Saudi Data and Artificial Intelligence Authority )

Registry name: NIC-SAIX-P-Cloud NIC (National Information Center)- SDAIA ( Saudi Data and Artificial Intelligence Authority ), SA · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 60.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS198795, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS198795, 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.
2a07:1f80:7::/48 No ROA RIR databaseRIPE 635 100% 67
2a07:1f80:8::/48 No ROA RIR databaseRIPE 635 100% 67
103.73.32.0/24 Valid Other origin only 673 100% 67
195.14.19.0/24 Valid Other origin only 673 100% 67
66.9.124.0/24 Valid RIR databaseRIPE 673 100% 67
77.236.120.0/21 Valid RIR databaseRIPE 673 100% 67
46.31.69.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

AS198795 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2a07:1f80:7::/48No ROA covers it. Add a ROA for AS198795, maxLength 48.635 of 636
ROA: none2a07:1f80:8::/48No ROA covers it. Add a ROA for AS198795, maxLength 48.635 of 636
Route object: none103.73.32.0/24Route objects for it name AS215861. Add a route object with origin AS198795 in the RIR database for the space.673 of 673
Route object: none195.14.19.0/24Route objects for it name AS25233, AS49610, AS58250. Add a route object with origin AS198795 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS198795 whose prefix no peer sees AS198795 announce. Many are kept on purpose (backup routes, space announced only in some places).

66.9.125.0/24RIPEValid
77.236.120.0/24RIPEInvalid: maxLength
2a07:1f80:6::/48RIPENo ROA
2a07:1f80:9::/48RIPENo 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.