bgpreport

Network · data from 2026-11-12

AS59126 NCT CO.,LTD.

Registry name: NCT - NCT CO.,LTD., JP · PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS59126, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS59126, 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.
193.114.0.0/20 No ROA Other IRR onlyJPIRR 672 100% 67
193.114.16.0/20 No ROA Other IRR onlyJPIRR 672 100% 67
103.81.144.0/22 No ROA Other IRR onlyJPIRR 670 100% 67
219.100.84.0/23 No ROA Other IRR onlyJPIRR 670 100% 67
219.100.86.0/23 No ROA Other IRR onlyJPIRR 670 100% 67
2400:7940::/32 No ROA Other IRR onlyJPIRR 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS59126: JPIRR::AS-NCT. 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 (AS59126 isn't in the set, or no route object for AS59126 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 objectsAS59126 in itNot covered
JPIRR::AS-NCT JPIRR 116 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 12 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none193.114.0.0/20No ROA covers it. Add a ROA for AS59126, maxLength 20.672 of 673
Route object: RIR193.114.0.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none193.114.16.0/20No ROA covers it. Add a ROA for AS59126, maxLength 20.672 of 673
Route object: RIR193.114.16.0/20Route object only in JPIRR. Add it in the RIR database for the space.672 of 673
ROA: none103.81.144.0/22No ROA covers it. Add a ROA for AS59126, maxLength 22.670 of 673
Route object: RIR103.81.144.0/22Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none219.100.84.0/23No ROA covers it. Add a ROA for AS59126, maxLength 23.670 of 673
Route object: RIR219.100.84.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none219.100.86.0/23No ROA covers it. Add a ROA for AS59126, maxLength 23.670 of 673
Route object: RIR219.100.86.0/23Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
ROA: none2400:7940::/32No ROA covers it. Add a ROA for AS59126, maxLength 32.634 of 636
Route object: RIR2400:7940::/32Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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