bgpreport

Network · data from 2026-11-12

AS399840 A&KK Group Inc

Registry name: AKK-GROUP-INC - A&KK Group Inc, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399840, 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:fed2:712a::/48 No ROA Other IRR onlyRADB 636 100% 68
192.43.246.0/24 Valid RIR databaseARIN, RADB 671 100% 67

AS-SET

AS399840'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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2602:fed2:712a::/48No ROA covers it. Add a ROA for AS399840, maxLength 48.636 of 636
Route object: RIR2602:fed2:712a::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2a06:a005:14e0::/44RADBNo ROA
2a0e:b107:18e0::/46RADBNo 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.