bgpreport

Network · data from 2026-11-12

AS210275 SITCO-AS Saudi Information Technology Company CJSC

Registry name: SITCO-AS Saudi Information Technology Company CJSC, SA · not in PeeringDB

14IPv4 routes 100.0% RPKI valid · 42.9% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 8 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS210275, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210275, 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.

176.105.148.0/24 Valid Nonecovered by 176.105.148.0/22 673 100% 67
176.105.149.0/24 Valid Nonecovered by 176.105.148.0/22 673 100% 67
176.105.151.0/24 Valid Nonecovered by 176.105.148.0/22 673 100% 67
185.35.78.0/24 Valid Nonecovered by 185.35.78.0/23 673 100% 67
185.169.32.0/24 Valid Nonecovered by 185.169.32.0/22 673 100% 67
176.105.150.0/24 Valid Nonecovered by 176.105.148.0/22 672 100% 67
185.35.79.0/24 Valid Nonecovered by 185.35.78.0/23 672 100% 67
185.169.35.0/24 Valid Nonecovered by 185.169.32.0/22 672 100% 67
83.229.65.0/24 Valid RIR databaseRIPE 673 100% 67
176.105.148.0/22 Valid RIR databaseRIPE 673 100% 67
185.35.78.0/23 Valid RIR databaseRIPE 673 100% 67
185.169.32.0/22 Valid RIR databaseRIPE 673 100% 67
185.169.33.0/24 Valid RIR databaseRIPE 673 100% 67
185.169.34.0/24 Valid RIR databaseRIPE 673 100% 67
2a13:2400::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS210275 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.

  • Route object: none8
ChangePrefix or setDetailFull-table peers
Route object: none176.105.148.0/24No route object for it. A route object for 176.105.148.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.673 of 673
Route object: none176.105.149.0/24No route object for it. A route object for 176.105.148.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.673 of 673
Route object: none176.105.151.0/24No route object for it. A route object for 176.105.148.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.673 of 673
Route object: none185.35.78.0/24No route object for it. A route object for 185.35.78.0/23 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.673 of 673
Route object: none185.169.32.0/24No route object for it. A route object for 185.169.32.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.673 of 673
Route object: none176.105.150.0/24No route object for it. A route object for 176.105.148.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.672 of 673
Route object: none185.35.79.0/24No route object for it. A route object for 185.35.78.0/23 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.672 of 673
Route object: none185.169.35.0/24No route object for it. A route object for 185.169.32.0/22 with origin AS210275 covers it (filters allowing more-specifics accept it). Add a route object with origin AS210275 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS210275 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.