bgpreport

Network · data from 2026-11-12

AS393780 Hyper Networks

Registry name: HYPER-ASNET - Hyper Networks LLC, US · PeeringDB

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

Announced routes

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

208.95.75.0/24 No ROA None 673 100% 67
208.89.166.0/23 Valid Nonecovered by 208.89.164.0/22 673 100% 67
64.124.3.0/24 Valid Other IRR onlyRADB 673 100% 67
104.245.17.0/24 Valid Other IRR onlyRADB 673 100% 67
104.245.18.0/23 Valid Other IRR onlyRADB 673 100% 67
192.198.31.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS393780'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 13 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none208.95.75.0/24No ROA covers it. Add a ROA for AS393780, maxLength 24.673 of 673
Route object: none208.95.75.0/24No route object for it. Add a route object with origin AS393780 in the RIR database for the space.673 of 673
Route object: none208.89.166.0/23No route object for it. A route object for 208.89.164.0/22 with origin AS393780 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393780 in the RIR database for the space.673 of 673
Route object: RIR64.124.3.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.245.17.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.245.18.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR192.198.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

38.70.216.0/24RADBNo ROA
192.198.28.0/23RADBNo ROA
192.198.28.0/24RADBNo ROA
208.89.164.0/22RADBNo ROA
2602:ff26::/36RADBNo ROA
2604:b480:fffe::/48RADBNo 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.