bgpreport

Network · data from 2026-11-12

AS29255 Etihad Etisalat

Registry name: ZAJIL-AS Etihad Etisalat, a joint stock company, SA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29255, 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.
82.147.192.0/19 Valid RIR databaseRADB, RIPE 673 100% 67
85.194.64.0/18 Valid RIR databaseRADB, RIPE 673 100% 66
89.237.128.0/18 Valid RIR databaseRADB, RIPE 673 100% 67
89.237.128.0/19 Valid RIR databaseRADB, RIPE 673 100% 67
89.237.176.0/20 Valid RIR databaseRADB, RIPE 673 100% 66
185.29.92.0/22 Valid RIR databaseRADB, RIPE 673 100% 66
212.24.224.0/19 Valid RIR databaseRADB, RIPE 673 100% 66
185.27.220.0/22 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS29255's PeeringDB record names no 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 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

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

37.216.192.0/19RIPEInvalid: origin
78.138.192.0/18RIPEInvalid: origin
85.194.64.0/19RIPEInvalid: maxLength
85.194.96.0/19RIPEInvalid: maxLength
89.237.160.0/19RIPEInvalid: maxLength
89.237.160.0/20RIPEInvalid: maxLength
194.50.35.0/24RIPEInvalid: origin
195.149.65.0/24RIPENo ROA
2a00:f580::/32RIPEInvalid: 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.