bgpreport

Network · data from 2026-11-12

AS202982 ASALRAJHIBANK Al-Rajhi Banking and Investment Corporation

Registry name: ASALRAJHIBANK Al-Rajhi Banking and Investment Corporation, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202982, 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.
185.148.148.0/24 Invalid: origin RIR databaseRIPE 0 0%low visibility 1
2a0a:2800:2::/47 No ROA RIR databaseRIPE 1 0%low visibility 1
2a0a:2800:2::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
2a0a:2800::/47 Valid RIR databaseRIPE 635 100% 67
2a0a:2800:255::/48 Valid RIR databaseRIPE 635 100% 68
2a0a:2800:254::/47 Valid RIR databaseRIPE 634 100% 67
2a0a:2800:1::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS202982 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 8 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin185.148.148.0/24ROAs covering it name AS19905, not AS202982. If AS202982 should announce it, add a ROA for AS202982.0 of 673
ROA: none2a0a:2800:2::/47No ROA covers it. Add a ROA for AS202982, maxLength 47.1 of 636
ROA: none2a0a:2800:2::/48No ROA covers it. Add a ROA for AS202982, maxLength 48.1 of 636

Route objects not announced

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

82.197.32.0/24RIPEInvalid: origin
82.197.33.0/24RIPEInvalid: origin
185.148.150.0/23RIPENo ROA
185.148.151.0/24RIPEInvalid: origin
193.19.90.0/23RIPENo 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.