bgpreport

Network · data from 2026-11-12

AS983 Akari Networks

Registry name: AKARI-NETWORKS - Akari Networks LLC, US · PeeringDB

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

Announced routes

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

2401:2120:983::/48 Valid Other IRR onlyRADB 634 100% 68
88.135.74.0/24 Valid RIR databaseRADB, RIPE 672 100% 68
103.172.40.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.172.40.0/24 Valid RIR databaseAPNIC, RADB 668 99% 68
2602:fbf1:c000::/36 Valid RIR databaseARIN, RADB 636 100% 69

AS-SET

PeeringDB's irr_as_set for AS983: RADB::AS-AKARI. 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 (AS983 isn't in the set, or no route object for AS983 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 objectsAS983 in itNot covered
RADB::AS-AKARI RADBlists itself further down15 member sets in no database: AS-ALANYHQ-NETWORKS, AS-LC, AS-NEBURST, AS131657:AS-FASTLINE, AS15143:AS-SET … 4371041,661 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 34 are in fix.csv.

  • Route object: RIR1
  • AS-SET: missing member15
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: RIR2401:2120:983::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS-ALANYHQ-NETWORKS; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS-LC; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS-NEBURST; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS131657:AS-FASTLINE; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS15143:AS-SET; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS1659:AS-TANET; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS201705:AS-XLINET; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS202959:AS-LUSHU; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS208223:AS-ALL; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS210352:AS-ZEROWOLF; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS211575:AS-RUINETWORK; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS213430:AS-CLOUDBASE-1; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS213605:AS-PYSIO-NETWORKS-TW; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS38254:AS-ITLAB; no IRR database read has it.
AS-SET: missing memberRADB::AS-AKARIAS-AKARI (RADB) lists AS917:AS-MISAKA; no IRR database read has it.

Route objects not announced

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

77.37.77.0/24RADB, RIPEValid
103.135.100.0/22APNICInvalid: origin
103.135.100.0/23APNICInvalid: origin
103.135.100.0/24APNICInvalid: origin
103.135.101.0/24APNICInvalid: origin
103.135.102.0/23APNICInvalid: origin
103.135.102.0/24APNICInvalid: origin
103.135.103.0/24APNICInvalid: origin
103.160.180.0/23APNICValid
103.160.180.0/24APNICValid
103.160.181.0/24APNICValid
103.172.41.0/24RADBValid
2001:470:21e::/48ARINValid
2001:470:294::/48ARINValid
2001:470:508::/48ARINValid
2407:cdc0::/32RADBValid
2407:cdc0:e019::/48RADBValid
2407:cdc0:eeee::/48APNIC, RADBValid

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.