bgpreport

Network · data from 2026-11-12

AS55393 MIDOKURA - Midokura Japan K.K.

Registry name: MIDOKURA - Midokura Japan K.K., JP · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55393, 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.
119.15.116.2/32 Invalid: maxLength Nonecovered by 119.15.116.0/24 1 0%low visibility 1
119.15.116.3/32 Invalid: maxLength Nonecovered by 119.15.116.0/24 1 0%low visibility 1
119.15.112.0/24 Valid None 673 100% 67
119.15.114.0/24 Valid Other IRR onlyJPIRR 672 100% 67
119.15.113.0/24 Valid Other IRR onlyJPIRR 671 100% 67
119.15.115.0/24 Valid Other IRR onlyJPIRR 671 100% 67
119.15.116.0/24 Valid Other IRR onlyJPIRR 671 100% 67

AS-SET

AS55393 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 10 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength119.15.116.2/32ROA 119.15.116.0/24 AS55393 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 119.15.116.2/32.1 of 673
Route object: none119.15.116.2/32No route object for it. A route object for 119.15.116.0/24 with origin AS55393 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55393 in the RIR database for the space.1 of 673
ROA: maxLength119.15.116.3/32ROA 119.15.116.0/24 AS55393 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 119.15.116.3/32.1 of 673
Route object: none119.15.116.3/32No route object for it. A route object for 119.15.116.0/24 with origin AS55393 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS55393 in the RIR database for the space.1 of 673
Route object: none119.15.112.0/24No route object for it. Add a route object with origin AS55393 in the RIR database for the space.673 of 673
Route object: RIR119.15.114.0/24Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR119.15.113.0/24Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR119.15.115.0/24Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR119.15.116.0/24Route object only in JPIRR. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

119.15.120.0/21RADBNo 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.