bgpreport

Network · data from 2026-11-12

AS204413 HYVE-UK Hyve Ltd

Registry name: HYVE-UK Hyve Ltd, GB · not in PeeringDB

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

Announced routes

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

45.11.218.0/23 No ROA Nonecovered by 45.11.216.0/22 673 100% 67
45.11.216.0/24 No ROA Nonecovered by 45.11.216.0/22 672 100% 67
2a0b:3540:2::/47 No ROA Nonecovered by 2a0b:3540::/29 605 95% 67
5.255.58.0/23 No ROA RIR databaseRIPE 673 100% 67
45.91.252.0/23 No ROA RIR databaseRIPE 673 100% 67
185.76.45.0/24 No ROA RIR databaseRIPE 673 100% 67
185.76.46.0/24 No ROA RIR databaseRIPE 673 100% 67
185.249.68.0/22 No ROA RIR databaseRIPE 673 100% 67
45.154.134.0/24 No ROA RIR databaseRIPE 672 100% 67
2a0b:3540::/47 No ROA RIR databaseRIPE 635 100% 67

AS-SET

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

  • ROA: none10
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none45.11.218.0/23No ROA covers it. Add a ROA for AS204413, maxLength 23.673 of 673
Route object: none45.11.218.0/23No route object for it. A route object for 45.11.216.0/22 with origin AS204413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204413 in the RIR database for the space.673 of 673
ROA: none45.11.216.0/24No ROA covers it. Add a ROA for AS204413, maxLength 24.672 of 673
Route object: none45.11.216.0/24No route object for it. A route object for 45.11.216.0/22 with origin AS204413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204413 in the RIR database for the space.672 of 673
ROA: none2a0b:3540:2::/47No ROA covers it. Add a ROA for AS204413, maxLength 47.605 of 636
Route object: none2a0b:3540:2::/47No route object for it. A route object for 2a0b:3540::/29 with origin AS204413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204413 in the RIR database for the space.605 of 636
ROA: none5.255.58.0/23No ROA covers it. Add a ROA for AS204413, maxLength 23.673 of 673
ROA: none45.91.252.0/23No ROA covers it. Add a ROA for AS204413, maxLength 23.673 of 673
ROA: none185.76.45.0/24No ROA covers it. Add a ROA for AS204413, maxLength 24.673 of 673
ROA: none185.76.46.0/24No ROA covers it. Add a ROA for AS204413, maxLength 24.673 of 673
ROA: none185.249.68.0/22No ROA covers it. Add a ROA for AS204413, maxLength 22.673 of 673
ROA: none45.154.134.0/24No ROA covers it. Add a ROA for AS204413, maxLength 24.672 of 673
ROA: none2a0b:3540::/47No ROA covers it. Add a ROA for AS204413, maxLength 47.635 of 636

Route objects not announced

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

45.11.216.0/22RIPENo ROA
45.91.252.0/24RIPENo ROA
45.91.253.0/24RIPENo ROA
185.249.68.0/24RIPENo ROA
185.249.69.0/24RIPENo ROA
185.249.70.0/24RIPENo ROA
185.249.71.0/24RIPENo ROA
2a0b:3540::/29RIPENo 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.