bgpreport

Network · data from 2026-11-12

AS15450 ALHAMBRA Alhambra Systems SA

Registry name: ALHAMBRA Alhambra Systems SA, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15450, 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.
209.99.50.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
84.246.169.0/24 No ROA RIR databaseRIPE 671 100% 67
195.138.209.0/24 No ROA RIR databaseRIPE 671 100% 67
199.58.191.0/24 No ROA RIR databaseARIN 671 100% 67
77.95.152.0/21 Valid RIR databaseRIPE 671 100% 67
91.240.173.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.64.0/21 Valid RIR databaseRIPE 671 100% 67
109.234.64.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.65.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.67.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.68.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.69.0/24 Valid RIR databaseRIPE 671 100% 67
109.234.70.0/24 Valid RIR databaseRIPE 671 100% 67
194.69.248.0/22 Valid RIR databaseRIPE 671 100% 67
194.69.248.0/24 Valid RIR databaseRIPE 671 100% 67
194.69.249.0/24 Valid RIR databaseRIPE 671 100% 67
194.69.251.0/24 Valid RIR databaseRIPE 671 100% 67
195.140.156.0/22 Valid RIR databaseRIPE 671 100% 67
195.140.156.0/24 Valid RIR databaseRIPE 671 100% 67
195.140.157.0/24 Valid RIR databaseRIPE 671 100% 67
195.140.158.0/24 Valid RIR databaseRIPE 671 100% 67
195.140.159.0/24 Valid RIR databaseRIPE 671 100% 67
77.95.152.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.153.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.154.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.155.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.156.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.157.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.158.0/24 Valid RIR databaseRIPE 670 100% 67
77.95.159.0/24 Valid RIR databaseRIPE 670 100% 67
109.234.66.0/24 Valid RIR databaseRIPE 670 100% 67
194.69.250.0/24 Valid RIR databaseRIPE 668 99% 67
2a01:7d00::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none209.99.50.0/24No ROA covers it. Add a ROA for AS15450, maxLength 24.671 of 673
Route object: RIR209.99.50.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none84.246.169.0/24No ROA covers it. Add a ROA for AS15450, maxLength 24.671 of 673
ROA: none195.138.209.0/24No ROA covers it. Add a ROA for AS15450, maxLength 24.671 of 673
ROA: none199.58.191.0/24No ROA covers it. Add a ROA for AS15450, maxLength 24.671 of 673

Route objects not announced

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

159.222.150.0/24ARINNo ROA
159.222.151.0/24ARINNo 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.