bgpreport

Network · data from 2026-11-12

AS39151 AXESS Hispasat Germany GmbH

Registry name: AXESS Hispasat Germany GmbH, DE · not in PeeringDB

14IPv4 routes 92.9% RPKI valid · 64.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS39151, seen from no peer

Announced routes

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

159.253.192.0/20 No ROA RIR databaseRADB, RIPE 673 100% 67
185.27.249.0/24 Valid None 673 100% 67
185.70.252.0/23 Valid Nonecovered by 185.70.252.0/22 673 100% 70
213.175.152.0/24 Valid Nonecovered by 213.175.128.0/19 673 100% 70
213.175.156.0/24 Valid Nonecovered by 213.175.128.0/19 673 100% 70
213.175.158.0/24 Valid Nonecovered by 213.175.128.0/19 673 100% 70
87.238.112.0/21 Valid RIR databaseRIPE 673 100% 70
91.151.144.0/20 Valid RIR databaseRIPE 673 100% 70
95.128.16.0/21 Valid RIR databaseRIPE 673 100% 70
213.175.128.0/24 Valid RIR databaseRIPE 673 100% 70
213.175.134.0/24 Valid RIR databaseRIPE 673 100% 70
213.175.136.0/21 Valid RIR databaseRIPE 673 100% 70
213.175.150.0/24 Valid RIR databaseRIPE 673 100% 67
213.208.32.0/21 Valid RIR databaseRADB, RIPE 673 100% 70

AS-SET

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

  • ROA: none1
  • Route object: none5
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none159.253.192.0/20No ROA covers it. Add a ROA for AS39151, maxLength 20.673 of 673
Route object: none185.27.249.0/24No route object for it. Add a route object with origin AS39151 in the RIR database for the space.673 of 673
Route object: none185.70.252.0/23No route object for it. A route object for 185.70.252.0/22 with origin AS39151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39151 in the RIR database for the space.673 of 673
Route object: none213.175.152.0/24No route object for it. A route object for 213.175.128.0/19 with origin AS39151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39151 in the RIR database for the space.673 of 673
Route object: none213.175.156.0/24No route object for it. A route object for 213.175.128.0/19 with origin AS39151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39151 in the RIR database for the space.673 of 673
Route object: none213.175.158.0/24No route object for it. A route object for 213.175.128.0/19 with origin AS39151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39151 in the RIR database for the space.673 of 673

Route objects not announced

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

41.205.230.0/24RADBNo ROA
91.151.144.0/24RIPEInvalid: maxLength
91.151.146.0/24RIPEInvalid: maxLength
91.151.147.0/24RIPEInvalid: maxLength
91.151.148.0/22RIPEInvalid: maxLength
91.151.152.0/23RIPEInvalid: maxLength
91.151.152.0/24RIPEInvalid: maxLength
91.151.153.0/24RIPEInvalid: maxLength
91.151.154.0/23RIPEInvalid: maxLength
91.151.154.0/24RIPEInvalid: maxLength
169.239.73.0/24RADBNo ROA
169.239.75.0/24RADBNo ROA
185.70.252.0/22RADBNo ROA
185.70.252.0/24RIPEValid
213.175.128.0/19RADBNo ROA
213.175.132.0/24RIPEValid

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.