bgpreport

Network · data from 2026-11-12

AS18071 MEI1 - Panasonic Information Systems Co., Ltd

Registry name: MEI1 - Panasonic Information Systems Co., Ltd, JP · not in PeeringDB

50IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
0Route objects not announced registered with origin AS18071, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18071, 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.

132.182.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.181.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.182.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.0.0/18 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.64.0/19 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.104.0/23 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.107.0/24 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.108.0/22 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.112.0/20 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.160.0/19 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.183.192.0/18 Valid Other IRR onlyJPIRR, RADB 672 100% 67
133.184.0.0/20 Valid Other IRR onlyJPIRR 672 100% 67
133.184.32.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.184.44.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.56.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.76.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.140.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.144.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.184.156.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.164.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.168.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.184.224.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.184.232.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.184.240.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.0.0/20 Valid Other IRR onlyJPIRR 672 100% 67
133.185.16.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.185.24.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.44.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.52.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.64.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.124.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.140.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.144.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.185.160.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.185.176.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.185.208.0/22 Valid Other IRR onlyJPIRR 672 100% 67
133.185.240.0/21 Valid Other IRR onlyJPIRR 672 100% 67
133.185.248.0/22 Valid Other IRR onlyJPIRR 672 100% 67
137.40.0.0/16 Valid Other IRR onlyJPIRR, RADB 672 100% 67
157.8.0.0/21 Valid Other IRR onlyJPIRR 672 100% 67
157.8.80.0/21 Valid Other IRR onlyJPIRR 672 100% 67
157.8.96.0/20 Valid Other IRR onlyJPIRR 672 100% 67
157.8.112.0/21 Valid Other IRR onlyJPIRR 672 100% 67
157.8.164.0/22 Valid Other IRR onlyJPIRR 672 100% 67
157.8.168.0/21 Valid Other IRR onlyJPIRR 672 100% 67
157.8.176.0/20 Valid Other IRR onlyJPIRR 672 100% 67
157.8.192.0/21 Valid Other IRR onlyJPIRR 672 100% 67
157.8.244.0/22 Valid Other IRR onlyJPIRR 672 100% 67
157.8.248.0/21 Valid Other IRR onlyJPIRR 672 100% 67
202.244.202.0/23 Valid Other IRR onlyJPIRR, RADB 672 100% 67

AS-SET

AS18071 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 50 are in fix.csv.

  • Route object: RIR50
ChangePrefix or setDetailFull-table peers
Route object: RIR132.182.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.181.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.182.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.0.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.64.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.104.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.107.0/24Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.108.0/22Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.112.0/20Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.160.0/19Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.183.192.0/18Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.32.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.44.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.56.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.76.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.140.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.144.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.156.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.164.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.168.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.224.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.232.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.184.240.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.16.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.24.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.44.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.52.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.64.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.124.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.140.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.144.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.160.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.176.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.208.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.240.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR133.185.248.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR137.40.0.0/16Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.0.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.80.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.96.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.112.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.164.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.168.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.176.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.192.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.244.0/22Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR157.8.248.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR202.244.202.0/23Route object only in JPIRR, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS18071 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.