bgpreport

Network · data from 2026-11-12

AS6914 HCSNET-ASNBLK - Hayes Computer Systems

Registry name: HCSNET-ASNBLK - Hayes Computer Systems, US · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
1IPv6 routes 100.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
0Route objects not announced registered with origin AS6914, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6914, 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.
207.156.16.0/24 No ROA RIR databaseARIN 673 100% 67
207.156.0.0/22 Valid RIR databaseARIN 673 100% 67
207.156.8.0/21 Valid RIR databaseARIN 673 100% 67
2605:e700:3000::/36 Valid RIR databaseARIN 604 95% 67

AS-SET

AS6914 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 1 are in fix.csv.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none207.156.16.0/24No ROA covers it. Add a ROA for AS6914, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS6914 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.