bgpreport

Network · data from 2026-11-12

AS20128 IN2 - iN2 LLC

Registry name: IN2 - iN2 LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20128, 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.
2605:7440::/32 No ROA Other origin only 634 100% 69
2605:7440::/33 No ROA Other origin only 634 100% 69
2605:7440:8000::/33 No ROA Other origin only 634 100% 69
66.180.48.0/20 No ROA Other IRR onlyNTTCOM 672 100% 67
66.180.48.0/21 No ROA Other IRR onlyNTTCOM 672 100% 67
66.180.56.0/21 No ROA Other IRR onlyNTTCOM 672 100% 67
66.180.48.0/22 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.48.0/23 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.48.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.52.0/22 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.56.0/22 No ROA Other IRR onlyNTTCOM 670 100% 67
66.180.60.0/22 No ROA Other IRR onlyNTTCOM 670 100% 67

AS-SET

AS20128 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 47 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none2605:7440::/32No ROA covers it. Add a ROA for AS20128, maxLength 32.634 of 636
Route object: none2605:7440::/32Route objects for it name AS7819. Add a route object with origin AS20128 in the RIR database for the space.634 of 636
ROA: none2605:7440::/33No ROA covers it. Add a ROA for AS20128, maxLength 33.634 of 636
Route object: none2605:7440::/33Route objects for it name AS7819. Add a route object with origin AS20128 in the RIR database for the space.634 of 636
ROA: none2605:7440:8000::/33No ROA covers it. Add a ROA for AS20128, maxLength 33.634 of 636
Route object: none2605:7440:8000::/33Route objects for it name AS7819. Add a route object with origin AS20128 in the RIR database for the space.634 of 636
ROA: none66.180.48.0/20No ROA covers it. Add a ROA for AS20128, maxLength 20.672 of 673
Route object: RIR66.180.48.0/20Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none66.180.48.0/21No ROA covers it. Add a ROA for AS20128, maxLength 21.672 of 673
Route object: RIR66.180.48.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none66.180.56.0/21No ROA covers it. Add a ROA for AS20128, maxLength 21.672 of 673
Route object: RIR66.180.56.0/21Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none66.180.48.0/22No ROA covers it. Add a ROA for AS20128, maxLength 22.670 of 673
Route object: RIR66.180.48.0/22Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none66.180.48.0/23No ROA covers it. Add a ROA for AS20128, maxLength 23.670 of 673
Route object: RIR66.180.48.0/23Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none66.180.48.0/24No ROA covers it. Add a ROA for AS20128, maxLength 24.670 of 673
Route object: RIR66.180.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none66.180.52.0/22No ROA covers it. Add a ROA for AS20128, maxLength 22.670 of 673
Route object: RIR66.180.52.0/22Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none66.180.56.0/22No ROA covers it. Add a ROA for AS20128, maxLength 22.670 of 673
Route object: RIR66.180.56.0/22Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none66.180.60.0/22No ROA covers it. Add a ROA for AS20128, maxLength 22.670 of 673
Route object: RIR66.180.60.0/22Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

66.180.32.0/19NTTCOMNo ROA
66.180.49.0/24NTTCOMNo ROA
66.180.50.0/23NTTCOMNo ROA
66.180.50.0/24NTTCOMNo ROA
66.180.51.0/24NTTCOMNo ROA
66.180.52.0/23NTTCOMNo ROA
66.180.52.0/24NTTCOMNo ROA
66.180.53.0/24NTTCOMNo ROA
66.180.54.0/23NTTCOMNo ROA
66.180.54.0/24NTTCOMNo ROA
66.180.55.0/24NTTCOMNo ROA
66.180.56.0/23NTTCOMNo ROA
66.180.56.0/24NTTCOMNo ROA
66.180.57.0/24NTTCOMNo ROA
66.180.58.0/23NTTCOMNo ROA
66.180.58.0/24NTTCOMNo ROA
66.180.59.0/24NTTCOMNo ROA
66.180.60.0/23NTTCOMNo ROA
66.180.60.0/24NTTCOMNo ROA
66.180.61.0/24NTTCOMNo ROA
66.180.62.0/23NTTCOMNo ROA
66.180.62.0/24NTTCOMNo ROA
66.180.63.0/24NTTCOMNo 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.