bgpreport

Network · data from 2026-11-12

AS135373

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135373, 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.
2404:ea80::/32 No ROA Other IRR onlyALTDB, NTTCOM, RADB 636 100% 68

AS-SET

AS135373 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 75 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced73
ChangePrefix or setDetailFull-table peers
ROA: none2404:ea80::/32No ROA covers it. Add a ROA for AS135373, maxLength 32.636 of 636
Route object: RIR2404:ea80::/32Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

69.172.68.0/24RADBNo ROA
69.172.71.0/24RADBNo ROA
69.172.72.0/24RADBNo ROA
103.215.188.0/22NTTCOM, RADBNo ROA
103.215.188.0/23NTTCOM, RADBNo ROA
103.215.188.0/24NTTCOM, RADBNo ROA
103.215.189.0/24NTTCOM, RADBNo ROA
103.215.190.0/23NTTCOM, RADBNo ROA
103.215.190.0/24NTTCOM, RADBNo ROA
103.215.191.0/24NTTCOM, RADBNo ROA
120.31.0.0/16RADBNo ROA
120.31.0.0/17RADBNo ROA
120.31.64.0/18RADBNo ROA
120.31.64.0/19NTTCOM, RADBNo ROA
120.31.64.0/20NTTCOM, RADBNo ROA
120.31.64.0/21NTTCOM, RADBNo ROA
120.31.64.0/22NTTCOM, RADBNo ROA
120.31.66.0/23RADBNo ROA
120.31.66.0/24RADBNo ROA
120.31.67.0/24RADBNo ROA
120.31.68.0/22RADBNo ROA
120.31.68.0/23RADBNo ROA
120.31.68.0/24RADBNo ROA
120.31.69.0/24RADBNo ROA
120.31.70.0/23RADBNo ROA
120.31.70.0/24RADBNo ROA
120.31.71.0/24RADBNo ROA
120.31.128.0/17RADBNo ROA
120.31.128.0/18RADBNo ROA
120.31.128.0/19NTTCOM, RADBNo ROA
120.31.128.0/20NTTCOM, RADBNo ROA
120.31.128.0/21RADBNo ROA
120.31.128.0/22RADBNo ROA
120.31.128.0/23NTTCOM, RADBNo ROA
120.31.128.0/24NTTCOM, RADBNo ROA
120.31.129.0/24NTTCOM, RADBNo ROA
120.31.130.0/23NTTCOM, RADBNo ROA
120.31.130.0/24NTTCOM, RADBNo ROA
120.31.131.0/24NTTCOM, RADBNo ROA
120.31.132.0/22RADBNo ROA
120.31.132.0/23NTTCOM, RADBNo ROA
120.31.132.0/24NTTCOM, RADBNo ROA
120.31.133.0/24NTTCOM, RADBNo ROA
120.31.134.0/23NTTCOM, RADBNo ROA
120.31.134.0/24NTTCOM, RADBNo ROA
120.31.135.0/24NTTCOM, RADBNo ROA
120.31.136.0/21RADBNo ROA
120.31.136.0/22RADBNo ROA
120.31.136.0/23NTTCOM, RADBNo ROA
120.31.136.0/24NTTCOM, RADBNo ROA
120.31.137.0/24NTTCOM, RADBNo ROA
120.31.138.0/23NTTCOM, RADBNo ROA
120.31.138.0/24NTTCOM, RADBNo ROA
120.31.139.0/24NTTCOM, RADBNo ROA
120.31.140.0/22RADBNo ROA
120.31.140.0/23RADBNo ROA
120.31.140.0/24NTTCOM, RADBNo ROA
120.31.141.0/24NTTCOM, RADBNo ROA
120.31.142.0/23NTTCOM, RADBNo ROA
120.31.142.0/24NTTCOM, RADBNo ROA
120.31.143.0/24NTTCOM, RADBNo ROA
120.31.144.0/20NTTCOM, RADBNo ROA
120.31.144.0/21NTTCOM, RADBNo ROA
120.31.144.0/22NTTCOM, RADBNo ROA
120.31.144.0/23NTTCOM, RADBNo ROA
120.31.144.0/24RADBNo ROA
157.119.72.0/22RADBNo ROA
157.119.72.0/23NTTCOM, RADBNo ROA
157.119.72.0/24NTTCOM, RADBNo ROA
157.119.73.0/24NTTCOM, RADBNo ROA
157.119.74.0/23NTTCOM, RADBNo ROA
157.119.74.0/24NTTCOM, RADBNo ROA
157.119.75.0/24NTTCOM, RADBNo 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.