bgpreport

Network · data from 2026-11-12

AS10001 mics network

Registry name: MICSNET - Mics Network Corporation, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10001, 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.
49.128.128.0/19 Valid Other IRR onlyJPIRR 672 100% 67
61.195.240.0/20 Valid Other IRR onlyJPIRR 672 100% 67
122.49.192.0/21 Valid Other IRR onlyJPIRR 672 100% 67
123.255.240.0/21 Valid Other IRR onlyJPIRR 672 100% 67
175.41.32.0/21 Valid Other IRR onlyJPIRR 672 100% 67
202.75.112.0/20 Valid Other IRR onlyJPIRR 672 100% 67
202.238.32.0/20 Valid Other IRR onlyJPIRR 672 100% 67
211.133.224.0/20 Valid Other IRR onlyJPIRR 672 100% 67
219.124.0.0/20 Valid Other IRR onlyJPIRR 672 100% 67
210.48.128.0/21 Valid Other IRR onlyJPIRR 671 100% 67
2403:7c00::/32 Valid Other IRR onlyJPIRR 634 100% 70

AS-SET

AS10001's PeeringDB record names no 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 15 are in fix.csv.

  • Route object: RIR11
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR49.128.128.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR61.195.240.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR122.49.192.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR123.255.240.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR175.41.32.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR202.75.112.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR202.238.32.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR211.133.224.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR219.124.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR210.48.128.0/21Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR2403:7c00::/32Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

61.195.240.0/21JPIRRInvalid: maxLength
61.195.248.0/21JPIRRInvalid: maxLength
219.124.0.0/21JPIRRInvalid: maxLength
219.124.8.0/21JPIRRInvalid: maxLength

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.