bgpreport

Network · data from 2026-11-12

AS56850 Akari Networks (UK)

Registry name: AKARI-AS Akari Networks Ltd, GB · PeeringDB

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

Announced routes

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

103.129.180.0/24 No ROA Other origin onlycovered by 103.129.180.0/22 152 23% 54
103.129.180.0/22 No ROA Other IRR onlyRADB 660 98% 67

AS-SET

PeeringDB's irr_as_set for AS56850: 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 (AS56850 isn't in the set, or no route object for AS56850 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 objectsAS56850 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 23 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • AS-SET: missing member15
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.129.180.0/24No ROA covers it. Add a ROA for AS56850, maxLength 24.152 of 673
Route object: none103.129.180.0/24Route objects for it name AS18049, AS134823. A route object for 103.129.180.0/22 with origin AS56850 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56850 in the RIR database for the space.152 of 673
ROA: none103.129.180.0/22No ROA covers it. Add a ROA for AS56850, maxLength 22.660 of 673
Route object: RIR103.129.180.0/22Route object only in RADB. Add it in the RIR database for the space.660 of 673
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 AS56850 whose prefix no peer sees AS56850 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.248.184.0/23RADBValid
185.248.184.0/24RADBValid
185.248.185.0/24RADBValid
2403:8340::/32RADBNo 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.