Network · data from 2026-11-12

AS203068 Bandalibre Comunicaciones

Registry name: BANDALIBRE-AS Bandalibre Comunicaciones, S.L., ES · PeeringDB

15IPv4 routes 80.0% RPKI valid · 93.3% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

3Route objects not announced registered with origin AS203068, seen from no peer

Announced routes

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


149.13.18.0/23	No ROA	Other IRR onlyRADB	673 100%	67
154.48.65.0/24	No ROA	Other IRR onlyRADB	673 100%	67
5.59.88.0/22	No ROA	RIR databaseRIPE	673 100%	67
88.148.88.0/24	Valid	None	673 100%	67
89.39.204.0/24	Valid	RIR databaseRIPE	673 100%	67
89.39.205.0/24	Valid	RIR databaseRIPE	673 100%	67
109.205.244.0/24	Valid	RIR databaseRIPE	673 100%	67
185.71.30.0/24	Valid	RIR databaseRIPE	673 100%	67
185.145.176.0/24	Valid	RIR databaseRIPE	673 100%	67
185.145.177.0/24	Valid	RIR databaseRIPE	673 100%	67
185.145.179.0/24	Valid	RIR databaseRIPE	673 100%	67
185.241.120.0/23	Valid	RIR databaseRIPE	673 100%	67
185.242.173.0/24	Valid	RIR databaseRIPE	673 100%	67
185.242.174.0/24	Valid	RIR databaseRIPE	673 100%	67
185.244.232.0/23	Valid	RIR databaseRIPE	673 100%	67

AS-SET

AS203068'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 9 are in fix.csv.

ROA: none3
Route object: none1
Route object: RIR2
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	149.13.18.0/23	No ROA covers it. Add a ROA for AS203068, maxLength 23.	673 of 673
Route object: RIR	149.13.18.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	154.48.65.0/24	No ROA covers it. Add a ROA for AS203068, maxLength 24.	673 of 673
Route object: RIR	154.48.65.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
ROA: none	5.59.88.0/22	No ROA covers it. Add a ROA for AS203068, maxLength 22.	673 of 673
Route object: none	88.148.88.0/24	No route object for it. Add a route object with origin AS203068 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

149.13.18.0/23

No ROA covers it. Add a ROA for AS203068, maxLength 23.

673 of 673

Route object: RIR

149.13.18.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

154.48.65.0/24

No ROA covers it. Add a ROA for AS203068, maxLength 24.

673 of 673

Route object: RIR

154.48.65.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

ROA: none

5.59.88.0/22

No ROA covers it. Add a ROA for AS203068, maxLength 22.

673 of 673

Route object: none

88.148.88.0/24

No route object for it. Add a route object with origin AS203068 in the RIR database for the space.

673 of 673

Route objects not announced

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


89.39.206.0/24	RIPE	Valid
89.39.207.0/24	RIPE	Valid
185.71.29.0/24	RIPE	Valid

89.39.206.0/24

RIPE

Valid

89.39.207.0/24

RIPE

Valid

185.71.29.0/24

RIPE

Valid

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.