bgpreport

Network · data from 2026-11-12

AS138384 Rakuten Mobile

Registry name: RMNI-AS-AP - Rakuten Mobile Network, Inc., JP · PeeringDB

31IPv4 routes 96.8% 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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS138384, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138384, 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.
202.216.0.0/20 No ROA Other IRR onlyJPIRR 672 100% 67
101.102.0.0/18 Valid Other IRR onlyJPIRR 672 100% 67
110.165.128.0/17 Valid Other IRR onlyJPIRR 672 100% 67
119.30.192.0/18 Valid Other IRR onlyJPIRR 672 100% 67
119.31.128.0/19 Valid Other IRR onlyJPIRR 672 100% 67
133.106.8.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.106.16.0/20 Valid Other IRR onlyJPIRR 672 100% 67
133.106.64.0/18 Valid Other IRR onlyJPIRR 672 100% 67
157.192.0.0/16 Valid Other IRR onlyJPIRR 672 100% 67
202.176.16.0/20 Valid Other IRR onlyJPIRR 672 100% 67
211.7.96.0/19 Valid Other IRR onlyJPIRR 672 100% 67
211.133.160.0/19 Valid Other IRR onlyJPIRR 672 100% 67
219.105.144.0/20 Valid Other IRR onlyJPIRR 672 100% 67
219.105.192.0/18 Valid Other IRR onlyJPIRR 672 100% 67
219.106.0.0/17 Valid Other IRR onlyJPIRR 672 100% 67
210.157.192.0/19 Valid Other IRR onlyJPIRR 671 100% 67
133.106.32.0/19 Valid Other IRR onlyJPIRR 669 99% 67
133.106.128.0/17 Valid Other IRR onlyJPIRR 669 99% 67
193.82.160.0/19 Valid RIR databaseAPNIC 672 100% 67
193.114.32.0/19 Valid RIR databaseAPNIC 672 100% 67
193.114.64.0/19 Valid RIR databaseAPNIC 672 100% 67
193.114.192.0/18 Valid RIR databaseAPNIC 672 100% 67
193.115.0.0/19 Valid RIR databaseAPNIC 672 100% 67
193.117.96.0/19 Valid RIR databaseAPNIC 672 100% 67
193.118.0.0/19 Valid RIR databaseAPNIC 672 100% 67
193.118.64.0/19 Valid RIR databaseAPNIC 672 100% 67
193.119.128.0/17 Valid RIR databaseAPNIC 672 100% 67
194.193.64.0/19 Valid RIR databaseAPNIC 672 100% 67
194.193.224.0/19 Valid RIR databaseAPNIC 672 100% 67
194.223.96.0/19 Valid RIR databaseAPNIC 672 100% 67
103.124.0.0/22 Valid RIR databaseAPNIC 670 100% 67
240b:c000::/24 Valid RIR databaseAPNIC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS138384: APNIC::AS138384:AS-RMI. 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 (AS138384 isn't in the set, or no route object for AS138384 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 objectsAS138384 in itNot covered
APNIC::AS138384:AS-RMI APNIC 41368 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 19 are in fix.csv.

  • ROA: none1
  • Route object: RIR18
ChangePrefix or setDetailFull-table peers
ROA: none202.216.0.0/20No ROA covers it. Add a ROA for AS138384, maxLength 20.672 of 673
Route object: RIR202.216.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.102.0.0/18Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR110.165.128.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR119.30.192.0/18Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR119.31.128.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.106.8.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.106.16.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.106.64.0/18Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.192.0.0/16Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR202.176.16.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR211.7.96.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR211.133.160.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR219.105.144.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR219.105.192.0/18Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR219.106.0.0/17Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR210.157.192.0/19Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR133.106.32.0/19Route object only in JPIRR. Add it in the RIR database for the space.669 of 673
Route object: RIR133.106.128.0/17Route object only in JPIRR. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS138384 is announced.

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.