bgpreport

Network · data from 2026-11-12

AS201769 ODC-COL ARABIAN INTERNET & COMMUNICATIONS SERVICES CO.LTD

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201769, 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.
78.93.50.0/24 Valid Nonecovered by 78.93.0.0/16 673 100% 67
185.114.68.0/24 Valid RIR databaseRIPE 673 100% 67
212.93.196.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS201769 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 10 are in fix.csv.

  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none78.93.50.0/24No route object for it. A route object for 78.93.0.0/16 with origin AS201769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201769 in the RIR database for the space.673 of 673

Route objects not announced

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

77.64.0.0/17RIPEInvalid: origin
78.93.0.0/16RIPEInvalid: origin
84.22.224.0/19RIPEInvalid: origin
86.60.0.0/17RIPENo ROA
185.114.68.0/22RIPENo ROA
212.93.192.0/19RIPEInvalid: origin
212.100.192.0/19RIPEInvalid: origin
212.116.192.0/19RIPEInvalid: origin
213.184.160.0/19RIPEInvalid: 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.