bgpreport

Network · data from 2026-11-12

AS18850 Hurricane Computer Solutions Inc.

Registry name: HDCS-AS-01 - Hurricane Computer Solutions Inc., CA · PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.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 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS18850, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18850, 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:f7a0::/36 No ROA None 630 99% 68
23.129.108.0/24 No ROA RIR databaseARIN 668 99% 67

AS-SET

AS18850's PeeringDB record names no 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: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2602:f7a0::/36No ROA covers it. Add a ROA for AS18850, maxLength 36.630 of 636
Route object: none2602:f7a0::/36No route object for it. Add a route object with origin AS18850 in the RIR database for the space.630 of 636
ROA: none23.129.108.0/24No ROA covers it. Add a ROA for AS18850, maxLength 24.668 of 673

Route objects not announced

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

75.98.7.0/24RADBNo ROA
206.132.208.0/24RADBNo 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.