bgpreport

Network · data from 2026-11-12

AS59127 Newmedia Corporation

Registry name: NCV - Newmedia Corporation, JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59127, 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.
2401:7ec0:1000::/36 Valid Nonecovered by 2401:7ec0::/32 634 100% 67
2401:7ec0:2000::/36 Valid Nonecovered by 2401:7ec0::/32 634 100% 67
2401:7ec0:3000::/36 Valid Nonecovered by 2401:7ec0::/32 634 100% 67
2401:7ec0:4000::/36 Valid Nonecovered by 2401:7ec0::/32 634 100% 67
61.44.128.0/19 Valid Other IRR onlyJPIRR 672 100% 67
61.44.160.0/19 Valid Other IRR onlyJPIRR 672 100% 67
101.203.0.0/19 Valid Other IRR onlyJPIRR 672 100% 67
101.203.0.0/20 Valid Other IRR onlyJPIRR 672 100% 67
101.203.16.0/21 Valid Other IRR onlyJPIRR 672 100% 67
101.203.24.0/21 Valid Other IRR onlyJPIRR 672 100% 67
101.203.32.0/20 Valid Other IRR onlyJPIRR 672 100% 67
113.197.40.0/21 Valid Other IRR onlyJPIRR 672 100% 67
113.213.192.0/19 Valid Other IRR onlyJPIRR 672 100% 67
113.213.224.0/20 Valid Other IRR onlyJPIRR 672 100% 67
116.199.240.0/20 Valid Other IRR onlyJPIRR 672 100% 67
122.200.136.0/21 Valid Other IRR onlyJPIRR 672 100% 67
180.92.16.0/20 Valid Other IRR onlyJPIRR 672 100% 67
180.148.144.0/21 Valid Other IRR onlyJPIRR 672 100% 67
216.171.112.0/20 Valid Other IRR onlyJPIRR 672 100% 67
223.223.240.0/20 Valid Other IRR onlyJPIRR 671 100% 67
2401:7ec0::/32 Valid Other IRR onlyJPIRR 634 100% 67

AS-SET

AS59127'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 22 are in fix.csv.

  • Route object: none4
  • Route object: RIR17
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2401:7ec0:1000::/36No route object for it. A route object for 2401:7ec0::/32 with origin AS59127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59127 in the RIR database for the space.634 of 636
Route object: none2401:7ec0:2000::/36No route object for it. A route object for 2401:7ec0::/32 with origin AS59127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59127 in the RIR database for the space.634 of 636
Route object: none2401:7ec0:3000::/36No route object for it. A route object for 2401:7ec0::/32 with origin AS59127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59127 in the RIR database for the space.634 of 636
Route object: none2401:7ec0:4000::/36No route object for it. A route object for 2401:7ec0::/32 with origin AS59127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59127 in the RIR database for the space.634 of 636
Route object: RIR61.44.128.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR61.44.160.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.203.0.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.203.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.203.16.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.203.24.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR101.203.32.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR113.197.40.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR113.213.192.0/19Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR113.213.224.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR116.199.240.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR122.200.136.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR180.92.16.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR180.148.144.0/21Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR216.171.112.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
Route object: RIR223.223.240.0/20Route object only in JPIRR. Add it in the RIR database for the space.671 of 673
Route object: RIR2401:7ec0::/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 AS59127 whose prefix no peer sees AS59127 announce. Many are kept on purpose (backup routes, space announced only in some places).

223.223.224.0/20JPIRRValid

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.