bgpreport

Network · data from 2026-11-12

AS198589 Al-Jazeera Al-Arabiya

Registry name: JT-AS Al-Jazeera Al-Arabiya Company for Communication and Internet LTD, IQ · PeeringDB

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

Announced routes

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

31.7.80.0/24 Valid Other origin onlycovered by 31.7.80.0/21 672 100% 67
5.62.144.0/23 Valid Nonecovered by 5.62.144.0/21 2 0%low visibility 2
5.62.133.0/24 Valid RIR databaseRIPE 672 100% 68
185.69.6.0/24 Valid RIR databaseRIPE 670 100% 67
5.62.140.0/24 Valid RIR databaseRIPE 669 99% 68
5.62.144.0/24 Valid RIR databaseRIPE 669 99% 68
5.62.150.0/24 Valid RIR databaseRIPE 669 99% 68
185.69.7.0/24 Valid RIR databaseRIPE 669 99% 67
5.62.143.0/24 Valid RIR databaseRIPE 668 99% 68
5.62.148.0/24 Valid RIR databaseRIPE 668 99% 68
5.62.130.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.131.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.132.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.135.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.138.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.139.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.141.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.142.0/24 Valid RIR databaseRIPE 667 99% 67
5.62.145.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.146.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.147.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.149.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.151.0/24 Valid RIR databaseRIPE 667 99% 68
5.62.137.0/24 Valid RIR databaseRIPE 128 19% 48
2a00:c9e0:1::/48 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS198589'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 36 are in fix.csv.

  • Route object: none2
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
Route object: none31.7.80.0/24Route objects for it name AS51020. A route object for 31.7.80.0/21 with origin AS198589 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198589 in the RIR database for the space.672 of 673
Route object: none5.62.144.0/23No route object for it. A route object for 5.62.144.0/21 with origin AS198589 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198589 in the RIR database for the space.2 of 673

Route objects not announced

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

5.62.128.0/20RIPENo ROA
5.62.128.0/21RIPEValid
5.62.128.0/24RIPEValid
5.62.129.0/24RIPEValid
5.62.134.0/24RIPEValid
5.62.136.0/21RIPENo ROA
5.62.136.0/24RIPEValid
5.62.144.0/21RIPEValid
31.7.80.0/21RIPENo ROA
31.7.81.0/24RIPEValid
31.7.82.0/24RIPEValid
31.7.84.0/24RIPEValid
31.7.85.0/24RIPEValid
31.7.86.0/24RIPEValid
31.7.87.0/24RIPEValid
37.77.48.0/21RIPEValid
37.77.48.0/22RIPEInvalid: maxLength
37.77.48.0/24RIPEInvalid: maxLength
37.77.49.0/24RIPEValid
37.77.50.0/24RIPEValid
37.77.51.0/24RIPEValid
37.77.52.0/24RIPEValid
37.77.53.0/24RIPEValid
37.77.54.0/24RIPEValid
37.77.55.0/24RIPEValid
185.69.4.0/22RIPEValid
2a00:c9e0::/29RIPENo ROA
2a00:c9e0::/32RIPEValid
2a00:c9e0:5::/48RIPEValid
2a00:c9e0:8::/48RIPEValid
2a00:c9e0:8000::/48RIPEValid
2a00:c9e0:8002::/48RIPEValid
2a00:c9e7::/32RIPENo ROA
2a00:c9e7:1::/48RIPEValid

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.