bgpreport

Network · data from 2026-11-12

AS58250 STCS-JDC ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD

Registry name: STCS-JDC ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD, SA · not in PeeringDB

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

Announced routes

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

195.10.197.0/24 No ROA RIR databaseRIPE 673 100% 67
78.93.117.0/24 Valid Nonecovered by 78.93.0.0/16 673 100% 67
86.60.32.0/19 Valid Nonecovered by 86.60.0.0/17 673 100% 67
78.93.82.0/23 Valid Nonecovered by 78.93.0.0/16 672 100% 67
78.93.178.0/24 Valid RIR databaseRIPE 673 100% 67
86.60.56.0/21 Valid RIR databaseRIPE 673 100% 67
212.93.203.0/24 Valid RIR databaseRIPE 673 100% 67
78.93.42.0/24 Valid RIR databaseRIPE 672 100% 67
86.60.127.0/24 Valid RIR databaseRIPE 672 100% 67
2a02:df4::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS58250 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 25 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none195.10.197.0/24No ROA covers it. Add a ROA for AS58250, maxLength 24.673 of 673
Route object: none78.93.117.0/24No route object for it. A route object for 78.93.0.0/16 with origin AS58250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58250 in the RIR database for the space.673 of 673
Route object: none86.60.32.0/19No route object for it. A route object for 86.60.0.0/17 with origin AS58250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58250 in the RIR database for the space.673 of 673
Route object: none78.93.82.0/23No route object for it. A route object for 78.93.0.0/16 with origin AS58250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58250 in the RIR database for the space.672 of 673

Route objects not announced

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

5.42.234.0/23RIPEValid
77.240.130.0/23RIPENo ROA
77.240.131.0/24RIPENo ROA
78.93.0.0/16RIPEInvalid: origin
78.93.107.0/24RIPEValid
78.93.108.0/23RIPEInvalid: origin
78.93.108.0/24RIPEValid
78.93.109.0/24RIPEValid
78.93.127.0/24RIPEInvalid: origin
78.93.160.0/24RIPEValid
78.93.161.0/24RIPEValid
86.60.0.0/17RIPENo ROA
89.189.224.0/19RIPENo ROA
91.217.212.0/24RIPEInvalid: origin
195.14.19.0/24RIPEInvalid: origin
212.93.192.0/19RIPEInvalid: origin
212.100.192.0/19RIPEInvalid: origin
212.100.223.0/24RIPEValid
212.116.192.0/19RIPEInvalid: origin
213.230.0.0/19RIPENo ROA
213.230.4.0/24RIPENo 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.