bgpreport

Network · data from 2026-11-12

AS51020 Al-Jazeera Wifi

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51020, 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.
37.77.48.0/23 Valid None 672 100% 67
37.77.52.0/23 Valid None 672 100% 67
185.69.4.0/23 Valid None 672 100% 67
5.62.128.0/23 Valid None 671 100% 67
5.62.136.0/23 Valid None 671 100% 67
31.7.80.0/23 Valid None 671 100% 67
31.7.84.0/23 Valid None 671 100% 67
31.7.86.0/23 Valid None 671 100% 67
37.77.50.0/23 Valid None 671 100% 67
5.62.128.0/24 Valid RIR databaseRIPE 672 100% 67
5.62.129.0/24 Valid RIR databaseRIPE 672 100% 67
31.7.82.0/24 Valid RIR databaseRIPE 672 100% 67
31.7.84.0/24 Valid RIR databaseRIPE 672 100% 67
31.7.85.0/24 Valid RIR databaseRIPE 672 100% 67
31.7.86.0/24 Valid RIR databaseRIPE 672 100% 67
31.7.87.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.48.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.49.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.50.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.52.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.53.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.55.0/24 Valid RIR databaseRIPE 672 100% 67
185.69.4.0/24 Valid RIR databaseRIPE 672 100% 67
185.69.5.0/24 Valid RIR databaseRIPE 672 100% 67
37.77.51.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS51020'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 16 are in fix.csv.

  • Route object: none9
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none37.77.48.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.672 of 673
Route object: none37.77.52.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.672 of 673
Route object: none185.69.4.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.672 of 673
Route object: none5.62.128.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673
Route object: none5.62.136.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673
Route object: none31.7.80.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673
Route object: none31.7.84.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673
Route object: none31.7.86.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673
Route object: none37.77.50.0/23No route object for it. Add a route object with origin AS51020 in the RIR database for the space.671 of 673

Route objects not announced

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

5.62.136.0/24RIPEValid
5.62.137.0/24RIPEValid
31.7.80.0/24RIPEValid
31.7.81.0/24RIPEValid
31.7.83.0/24RIPEInvalid: maxLength
37.77.54.0/24RIPEValid
185.21.139.0/24RIPEInvalid: 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.