bgpreport

Network · data from 2026-11-12

AS394566 ALEGEUS-AS - ALEGEUS TECHNOLOGIES, LLC

Registry name: ALEGEUS-AS - ALEGEUS TECHNOLOGIES, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394566, 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.
2620:ff:4000::/48 No ROA Other origin only 634 100% 69
198.252.169.0/24 No ROA Other IRR onlyRADB 671 100% 67
131.153.39.0/24 Valid None 670 100% 67

AS-SET

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

  • ROA: none2
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2620:ff:4000::/48No ROA covers it. Add a ROA for AS394566, maxLength 48.634 of 636
Route object: none2620:ff:4000::/48Route objects for it name AS14135. Add a route object with origin AS394566 in the RIR database for the space.634 of 636
ROA: none198.252.169.0/24No ROA covers it. Add a ROA for AS394566, maxLength 24.671 of 673
Route object: RIR198.252.169.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none131.153.39.0/24No route object for it. Add a route object with origin AS394566 in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS394566 is announced.

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.