bgpreport

Network · data from 2026-11-12

AS215691 HOSTEALO

Registry name: HOSTEALO AP INTERACTIVE SOLUTIONS SL, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215691, 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.
154.58.206.0/24 No ROA Other IRR onlyRADB 673 100% 67
212.47.59.0/24 Valid None 673 100% 67
2a14:8880::/29 Valid None 631 99% 67
154.202.74.0/24 Valid Other IRR onlyRADB 671 100% 66
2.27.237.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
78.40.111.0/24 Valid RIR databaseRIPE 673 100% 67
151.242.190.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
171.22.18.0/24 Valid RIR databaseRIPE 673 100% 67
193.8.185.0/24 Valid RIR databaseRIPE 673 100% 67
45.157.211.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
45.198.54.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
45.198.55.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
79.110.63.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS215691'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 6 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none154.58.206.0/24No ROA covers it. Add a ROA for AS215691, maxLength 24.673 of 673
Route object: RIR154.58.206.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none212.47.59.0/24No route object for it. Add a route object with origin AS215691 in the RIR database for the space.673 of 673
Route object: none2a14:8880::/29No route object for it. Add a route object with origin AS215691 in the RIR database for the space.631 of 636
Route object: RIR154.202.74.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2a12:de40:38::/48RIPENo 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.