bgpreport

Network · data from 2026-11-12

AS59451 ARABBANK-AS Al-Bank Al-Arabi PLC. CO.

Registry name: ARABBANK-AS Al-Bank Al-Arabi PLC. CO., JO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59451, 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.75.150.0/24 No ROA Nonecovered by 37.75.144.0/21 672 100% 67
185.173.58.0/24 No ROA RIR databaseRIPE 673 100% 67
185.173.59.0/24 No ROA RIR databaseRIPE 673 100% 67
37.75.145.0/24 No ROA RIR databaseRIPE 672 100% 67
37.75.147.0/24 No ROA RIR databaseRADB, RIPE 672 100% 67
37.75.149.0/24 No ROA RIR databaseRIPE 671 100% 67
194.165.131.0/24 Valid Other origin only 672 100% 67
185.173.56.0/24 Valid RIR databaseRIPE 673 100% 67
37.75.144.0/24 Valid RIR databaseRIPE 672 100% 67
37.75.146.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67

AS-SET

AS59451 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.

  • ROA: none6
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none37.75.150.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.672 of 673
Route object: none37.75.150.0/24No route object for it. A route object for 37.75.144.0/21 with origin AS59451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59451 in the RIR database for the space.672 of 673
ROA: none185.173.58.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.673 of 673
ROA: none185.173.59.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.673 of 673
ROA: none37.75.145.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.672 of 673
ROA: none37.75.147.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.672 of 673
ROA: none37.75.149.0/24No ROA covers it. Add a ROA for AS59451, maxLength 24.671 of 673
Route object: none194.165.131.0/24Route objects for it name AS8376, AS8697. Add a route object with origin AS59451 in the RIR database for the space.672 of 673

Route objects not announced

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

37.75.144.0/21RADB, RIPENo ROA
185.173.56.0/22RIPENo 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.