Network · data from 2026-11-12
AS400951 AKARI-NETWORKS - Akari Networks LLC
Registry name: AKARI-NETWORKS - Akari Networks LLC, US · not in PeeringDB
40IPv4 routes
92.5% RPKI valid · 70.0% with a route object
0IPv6 routes
3RPKI invalid
3 origin · 0 maxLength
0No ROA
12 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS400951, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS400951, 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.
| 212.74.6.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 212.74.6.0/24 | Invalid: origin | None | 2 0%low visibility |
| 212.74.7.0/24 | Invalid: origin | None | 2 0%low visibility |
| 13.141.70.0/24 | Valid | Nonecovered by 13.141.70.0/23 | 669 99% |
| 13.141.71.0/24 | Valid | Nonecovered by 13.141.70.0/23 | 669 99% |
| 87.84.188.0/24 | Valid | Nonecovered by 87.84.188.0/23 | 669 99% |
| 87.84.189.0/24 | Valid | Nonecovered by 87.84.188.0/23 | 669 99% |
| 155.117.198.0/24 | Valid | Nonecovered by 155.117.198.0/23 | 669 99% |
| 155.117.199.0/24 | Valid | Nonecovered by 155.117.198.0/23 | 669 99% |
| 212.189.50.0/24 | Valid | Nonecovered by 212.189.50.0/23 | 669 99% |
| 212.189.51.0/24 | Valid | Nonecovered by 212.189.50.0/23 | 669 99% |
| 217.217.7.0/24 | Valid | Nonecovered by 217.217.6.0/23 | 669 99% |
| 212.189.50.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 13.141.70.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 87.84.188.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 169.40.124.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 189.24.122.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 189.24.122.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 189.24.123.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 198.84.0.0/22 | Valid | RIR databaseARIN | 669 99% |
| 217.217.6.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 64.83.60.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 64.83.62.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 64.178.122.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 155.117.198.0/23 | Valid | RIR databaseRADB, RIPE | 668 99% |
| 64.178.112.0/23 | Valid | RIR databaseRADB, RIPE | 667 99% |
| 64.178.124.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 64.178.126.0/23 | Valid | RIR databaseRIPE | 667 99% |
| 64.83.60.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.83.61.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.83.62.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.83.63.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.112.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.113.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.122.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.123.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.124.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.125.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.126.0/24 | Valid | RIR databaseRIPE | 169 25% |
| 64.178.127.0/24 | Valid | RIR databaseRIPE | 169 25% |
AS-SET
AS400951 isn't in PeeringDB, where networks name their 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 19 are in fix.csv.
- ROA: origin3
- Route object: none12
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.74.6.0/23 | ROAs covering it name AS834, not AS400951. If AS400951 should announce it, add a ROA for AS400951. |
| Route object: none | 212.74.6.0/23 | Route objects for it name AS834. Add a route object with origin AS400951 in the RIR database for the space. |
| ROA: origin | 212.74.6.0/24 | ROAs covering it name AS834, not AS400951. If AS400951 should announce it, add a ROA for AS400951. |
| Route object: none | 212.74.6.0/24 | No route object for it. Add a route object with origin AS400951 in the RIR database for the space. |
| ROA: origin | 212.74.7.0/24 | ROAs covering it name AS834, not AS400951. If AS400951 should announce it, add a ROA for AS400951. |
| Route object: none | 212.74.7.0/24 | No route object for it. Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 13.141.70.0/24 | No route object for it. A route object for 13.141.70.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 13.141.71.0/24 | No route object for it. A route object for 13.141.70.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 87.84.188.0/24 | No route object for it. A route object for 87.84.188.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 87.84.189.0/24 | No route object for it. A route object for 87.84.188.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 155.117.198.0/24 | No route object for it. A route object for 155.117.198.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 155.117.199.0/24 | No route object for it. A route object for 155.117.198.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 212.189.50.0/24 | No route object for it. A route object for 212.189.50.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 212.189.51.0/24 | No route object for it. A route object for 212.189.50.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: none | 217.217.7.0/24 | No route object for it. A route object for 217.217.6.0/23 with origin AS400951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400951 in the RIR database for the space. |
| Route object: RIR | 212.189.50.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400951 whose prefix no peer sees AS400951 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.185.208.0/24 | ARIN | Invalid: origin |
| 64.83.56.0/22 | RIPE | Valid |
| 64.83.60.0/22 | RIPE | Valid |
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.