Network · data from 2026-11-12

AS30857 CITC-AS Communications, Space & Technology Commission (Saudi Arabia)

Registry name: CITC-AS Communications, Space & Technology Commission (Saudi Arabia), SA · not in PeeringDB

11IPv4 routes 100.0% RPKI valid · 72.7% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

5Route objects not announced registered with origin AS30857, seen from no peer

Announced routes

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


86.111.196.0/23	Valid	Nonecovered by 86.111.192.0/21	673 100%	67
86.111.196.0/24	Valid	Nonecovered by 86.111.192.0/21	673 100%	67
86.111.197.0/24	Valid	Nonecovered by 86.111.192.0/21	673 100%	67
91.206.134.0/24	Valid	RIR databaseRIPE	673 100%	67
91.206.135.0/24	Valid	RIR databaseRIPE	673 100%	67
86.111.192.0/22	Valid	RIR databaseRADB, RIPE	672 100%	67
91.206.134.0/23	Valid	RIR databaseRADB, RIPE	672 100%	67
86.111.192.0/24	Valid	RIR databaseRIPE	671 100%	67
86.111.193.0/24	Valid	RIR databaseRIPE	671 100%	67
86.111.194.0/24	Valid	RIR databaseRIPE	671 100%	67
86.111.195.0/24	Valid	RIR databaseRIPE	671 100%	67
2001:67c:130::/48	Valid	RIR databaseRADB, RIPE	634 100%	67
2001:67c:18c8::/47	Valid	RIR databaseRADB, RIPE	632 99%	67

AS-SET

AS30857 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: none3
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	86.111.196.0/23	No route object for it. A route object for 86.111.192.0/21 with origin AS30857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30857 in the RIR database for the space.	673 of 673
Route object: none	86.111.196.0/24	No route object for it. A route object for 86.111.192.0/21 with origin AS30857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30857 in the RIR database for the space.	673 of 673
Route object: none	86.111.197.0/24	No route object for it. A route object for 86.111.192.0/21 with origin AS30857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30857 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

86.111.196.0/23

No route object for it. A route object for 86.111.192.0/21 with origin AS30857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30857 in the RIR database for the space.

673 of 673

Route object: none

86.111.196.0/24

673 of 673

Route object: none

86.111.197.0/24

673 of 673

Route objects not announced

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


86.111.192.0/21	RADB, RIPE	No ROA
86.111.194.0/23	RIPE	Invalid: maxLength
86.111.199.0/24	RADB, RIPE	No ROA
194.0.15.0/24	RADB, RIPE	No ROA
2001:1490:100::/48	RIPE	Invalid: origin

86.111.192.0/21

RADB, RIPE

No ROA

86.111.194.0/23

RIPE

Invalid: maxLength

86.111.199.0/24

RADB, RIPE

No ROA

194.0.15.0/24

RADB, RIPE

No ROA

2001:1490:100::/48

RIPE

Invalid: origin

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.