bgpreport

Network · data from 2026-11-12

AS18944 HEAP - AS18944 LLC

Registry name: HEAP - AS18944 LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18944, 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:fbfe::/48 Valid Nonecovered by 2602:fbfe::/36 630 99% 69
141.193.244.0/24 Valid RIR databaseARIN, RADB 667 99% 66

AS-SET

AS18944 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 2 are in fix.csv.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2602:fbfe::/48No route object for it. A route object for 2602:fbfe::/36 with origin AS18944 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18944 in the RIR database for the space.630 of 636

Route objects not announced

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

2602:fbfe::/36ARIN, RADBValid

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.