bgpreport

Network · data from 2026-11-12

AS400429 ALTHEA - Hawk Networks Inc

Registry name: ALTHEA - Hawk Networks Inc, US · not in PeeringDB

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

Announced routes

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

2602:fbad:10::/45 No ROA RIR databaseARIN 634 100% 69

AS-SET

AS400429 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: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2602:fbad:10::/45No ROA covers it. Add a ROA for AS400429, maxLength 45.634 of 636

Route objects not announced

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

23.139.56.0/24ARINNo ROA
2001:470:2b5::/48ARINValid
2602:fbad::/45ARINNo ROA
2602:fbad:8::/45ARINNo 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.