bgpreport

Network · data from 2026-11-12

AS7690 Mirai Communication Network inc.,

Registry name: MIRAI - Mirai Communication Network Inc., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7690, 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.26.24.0/23 No ROA Other IRR onlyJPIRR 670 100% 67
103.232.22.0/23 No ROA Other IRR onlyJPIRR 670 100% 67
218.231.246.0/23 No ROA Other IRR onlyJPIRR 669 99% 67
123.103.224.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
158.199.112.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
210.156.176.0/20 Valid Other IRR onlyJPIRR, RADB 671 100% 67
210.172.192.0/19 Valid Other IRR onlyJPIRR, RADB 671 100% 67
202.240.84.0/23 Valid Other IRR onlyJPIRR, RADB 670 100% 67
123.103.128.0/18 Valid Other IRR onlyJPIRR, RADB 669 99% 67
2407:d600::/32 Valid Other IRR onlyJPIRR, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS7690: JPIRR::AS-MIRAI. 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 (AS7690 isn't in the set, or no route object for AS7690 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 objectsAS7690 in itNot covered
JPIRR::AS-MIRAI JPIRR 3120 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 21 are in fix.csv.

  • ROA: none3
  • Route object: RIR10
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none103.26.24.0/23No ROA covers it. Add a ROA for AS7690, maxLength 23.670 of 673
Route object: RIR103.26.24.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none103.232.22.0/23No ROA covers it. Add a ROA for AS7690, maxLength 23.670 of 673
Route object: RIR103.232.22.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none218.231.246.0/23No ROA covers it. Add a ROA for AS7690, maxLength 23.669 of 673
Route object: RIR218.231.246.0/23Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR123.103.224.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR158.199.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR210.156.176.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR210.172.192.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR202.240.84.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR123.103.128.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2407:d600::/32Route object only in JPIRR, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.112.4.0/22RADBNo ROA
45.114.208.0/22RADBNo ROA
45.120.176.0/22RADBNo ROA
103.242.84.0/22RADBNo ROA
103.252.116.0/22RADBNo ROA
103.253.100.0/22RADBNo ROA
133.155.0.0/17RADBNo ROA
158.199.64.0/18RADBNo 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.