bgpreport

Network · data from 2026-11-19

AS401386 Hyper Group Network LLC.

Registry name: HYPERGROUP-NET - Hyper Group Network LLC, US · PeeringDB

0IPv4 routes
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
31Route objects not announced registered with origin AS401386, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS401386, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.

2602:f7dc:202::/48 Valid Nonecovered by 2602:f7dc:200::/40 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS401386: AS401386:AS-HN-NET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS401386 isn't in the set, or no route object for AS401386 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS401386 in itNot covered
AS401386:AS-HN-NET ARIN 1131 Yes 0

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

  • Route object: none1
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
Route object: none2602:f7dc:202::/48No route object for it. A route object for 2602:f7dc:200::/40 with origin AS401386 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401386 in the RIR database for the space.633 of 633

Route objects not announced

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

2602:f613:20::/44ARINInvalid: origin
2602:f7dc::/48ARINInvalid: origin
2602:f7dc:1::/48ARINInvalid: origin
2602:f7dc:2::/48ARINInvalid: origin
2602:f7dc:200::/40ARINValid
2a0f:85c1:351::/48RIPEInvalid: origin
2a14:7581:2000::/36RIPENo ROA
2a14:7581:2000::/40RIPEValid
2a14:7581:2100::/40RIPEValid
2a14:7581:2111::/48RIPEInvalid: maxLength
2a14:7581:2119::/48RIPEInvalid: maxLength
2a14:7581:2124::/48RIPEInvalid: maxLength
2a14:7581:2153::/48RIPEInvalid: maxLength
2a14:7581:2199::/48RIPEInvalid: maxLength
2a14:7581:2200::/40RIPEValid
2a14:7581:2228::/48RIPEInvalid: maxLength
2a14:7581:2233::/48RIPEInvalid: maxLength
2a14:7581:2234::/48RIPEInvalid: maxLength
2a14:7581:2245::/48RIPEInvalid: maxLength
2a14:7581:2280::/48RIPEInvalid: maxLength
2a14:7581:2300::/40RIPEValid
2a14:7581:2300::/48RIPEInvalid: maxLength
2a14:7581:2301::/48RIPEInvalid: maxLength
2a14:7581:2310::/48RIPEInvalid: maxLength
2a14:7581:2320::/48RIPEInvalid: maxLength
2a14:7581:2323::/48RIPEInvalid: maxLength
2a14:7581:2332::/48RIPEInvalid: maxLength
2a14:7581:2350::/48RIPEInvalid: maxLength
2a14:7581:2368::/48RIPEInvalid: maxLength
2a14:7581:2f00::/48RIPEValid
2a14:7581:2f01::/48RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-19 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.