bgpreport

Network · data from 2026-11-12

AS59116 AIGTKK - AIG Technologies KK

Registry name: AIGTKK - AIG Technologies KK, JP · not in PeeringDB

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

Announced routes

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

2620:13f:700e::/48 No ROA Other origin onlycovered by 2620:13f:700e::/47 635 100% 69
170.105.8.0/24 No ROA Other IRR onlyRADB 673 100% 67
170.105.12.0/22 No ROA Other IRR onlyRADB 673 100% 67
170.105.16.0/22 No ROA Other IRR onlyRADB 673 100% 67
170.105.18.0/24 No ROA Other IRR onlyRADB 671 100% 68
170.105.26.0/24 No ROA Other IRR onlyRADB 671 100% 68
170.105.27.0/24 No ROA Other IRR onlyRADB 671 100% 68
170.105.10.0/24 No ROA Other IRR onlyRADB 670 100% 67
170.105.20.0/24 No ROA Other IRR onlyRADB 670 100% 68
170.105.21.0/24 No ROA Other IRR onlyRADB 670 100% 68
170.105.24.0/22 No ROA Other IRR onlyRADB 670 100% 67
170.105.30.0/24 No ROA Other IRR onlyRADB 670 100% 67
170.105.29.0/24 No ROA Other IRR onlyRADB 669 99% 67
2620:13f:701c::/48 No ROA Other IRR onlyRADB 635 100% 70
2620:13f:700c::/47 No ROA Other IRR onlyNTTCOM, RADB 634 100% 70
2620:13f:700e::/47 No ROA Other IRR onlyNTTCOM, RADB 634 100% 67
2620:13f:701e::/48 No ROA Other IRR onlyRADB 628 99% 67

AS-SET

AS59116 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 38 are in fix.csv.

  • ROA: none17
  • Route object: none1
  • Route object: RIR16
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2620:13f:700e::/48No ROA covers it. Add a ROA for AS59116, maxLength 48.635 of 636
Route object: none2620:13f:700e::/48Route objects for it name AS19551. A route object for 2620:13f:700e::/47 with origin AS59116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59116 in the RIR database for the space.635 of 636
ROA: none170.105.8.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.673 of 673
Route object: RIR170.105.8.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.105.12.0/22No ROA covers it. Add a ROA for AS59116, maxLength 22.673 of 673
Route object: RIR170.105.12.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.105.16.0/22No ROA covers it. Add a ROA for AS59116, maxLength 22.673 of 673
Route object: RIR170.105.16.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.105.18.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.671 of 673
Route object: RIR170.105.18.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.105.26.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.671 of 673
Route object: RIR170.105.26.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.105.27.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.671 of 673
Route object: RIR170.105.27.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none170.105.10.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.670 of 673
Route object: RIR170.105.10.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.105.20.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.670 of 673
Route object: RIR170.105.20.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.105.21.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.670 of 673
Route object: RIR170.105.21.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.105.24.0/22No ROA covers it. Add a ROA for AS59116, maxLength 22.670 of 673
Route object: RIR170.105.24.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.105.30.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.670 of 673
Route object: RIR170.105.30.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none170.105.29.0/24No ROA covers it. Add a ROA for AS59116, maxLength 24.669 of 673
Route object: RIR170.105.29.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2620:13f:701c::/48No ROA covers it. Add a ROA for AS59116, maxLength 48.635 of 636
Route object: RIR2620:13f:701c::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2620:13f:700c::/47No ROA covers it. Add a ROA for AS59116, maxLength 47.634 of 636
Route object: RIR2620:13f:700c::/47Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
ROA: none2620:13f:700e::/47No ROA covers it. Add a ROA for AS59116, maxLength 47.634 of 636
Route object: RIR2620:13f:700e::/47Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
ROA: none2620:13f:701e::/48No ROA covers it. Add a ROA for AS59116, maxLength 48.628 of 636
Route object: RIR2620:13f:701e::/48Route object only in RADB. Add it in the RIR database for the space.628 of 636

Route objects not announced

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

2620:13f:700d::/48NTTCOMNo ROA
2620:13f:700f::/48NTTCOMNo ROA
2620:13f:701d::/48RADBNo ROA
2620:13f:701f::/48RADBNo ROA

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.