bgpreport

Network · data from 2026-11-12

AS151195 Nova Global ICT Kabushiki Kaisha

Registry name: NGIKK-AS-AP - Nova Global ICT Kabushiki Kaisha, JP · PeeringDB

3IPv4 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
25Route objects not announced registered with origin AS151195, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS151195, 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.
199.166.24.0/21 Valid RIR databaseAPNIC 554 82% 68
45.251.67.0/24 Valid RIR databaseAPNIC 536 80% 68
103.206.88.0/22 Valid RIR databaseAPNIC 536 80% 68
2401:3e0::/32 Valid RIR databaseAPNIC 169 27% 41

AS-SET

AS151195'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 25 are in fix.csv.

  • Route object: not announced25

Route objects not announced

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

66.160.164.0/24ARINValid
72.52.111.0/24ARINValid
103.206.88.0/23APNICValid
103.206.88.0/24APNICValid
103.206.89.0/24APNICValid
103.206.90.0/23APNICValid
103.206.90.0/24APNICValid
103.206.91.0/24APNICValid
199.166.24.0/22APNICValid
199.166.24.0/23APNICValid
199.166.24.0/24APNICValid
199.166.25.0/24APNICValid
199.166.26.0/23APNICValid
199.166.26.0/24APNICValid
199.166.27.0/24APNICValid
199.166.28.0/22APNICValid
199.166.28.0/23APNICValid
199.166.28.0/24APNICValid
199.166.29.0/24APNICValid
199.166.30.0/23APNICValid
199.166.30.0/24APNICValid
199.166.31.0/24APNICValid
2001:470:2cd::/48ARINValid
2001:470:5e9::/48ARINValid
2001:470:5f3::/48ARINValid

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.