bgpreport

Network · data from 2026-11-12

AS7306 ASIANDEVBANK - Asian Development Bank

Registry name: ASIANDEVBANK - Asian Development Bank, US · not in PeeringDB

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

Announced routes

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

202.4.4.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
202.4.10.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
202.4.0.0/21 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
202.4.0.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
202.4.8.0/23 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
202.4.9.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
202.4.0.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.1.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.2.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.3.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.4.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.5.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.6.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.7.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.8.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.10.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
202.4.11.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2

AS-SET

AS7306 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 73 are in fix.csv.

  • ROA: none17
  • Route object: RIR17
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none202.4.4.0/22No ROA covers it. Add a ROA for AS7306, maxLength 22.673 of 673
Route object: RIR202.4.4.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.4.10.0/23No ROA covers it. Add a ROA for AS7306, maxLength 23.673 of 673
Route object: RIR202.4.10.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none202.4.0.0/21No ROA covers it. Add a ROA for AS7306, maxLength 21.671 of 673
Route object: RIR202.4.0.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.4.0.0/22No ROA covers it. Add a ROA for AS7306, maxLength 22.671 of 673
Route object: RIR202.4.0.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.4.8.0/23No ROA covers it. Add a ROA for AS7306, maxLength 23.671 of 673
Route object: RIR202.4.8.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.4.9.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.671 of 673
Route object: RIR202.4.9.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none202.4.0.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.0.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.1.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.1.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.2.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.2.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.3.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.3.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.4.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.4.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.5.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.5.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.6.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.6.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.7.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.7.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.8.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.8.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.10.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.10.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none202.4.11.0/24No ROA covers it. Add a ROA for AS7306, maxLength 24.2 of 673
Route object: RIR202.4.11.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

192.227.1.0/24NTTCOMNo ROA
192.227.2.0/23NTTCOMNo ROA
192.227.4.0/22NTTCOMNo ROA
192.227.8.0/21NTTCOMNo ROA
202.0.16.0/20NTTCOMNo ROA
202.0.16.0/22NTTCOM, RADBNo ROA
202.0.16.0/24NTTCOMNo ROA
202.0.17.0/24NTTCOMNo ROA
202.0.18.0/24NTTCOMNo ROA
202.0.19.0/24NTTCOMNo ROA
202.0.20.0/24NTTCOMNo ROA
202.0.21.0/24NTTCOMNo ROA
202.0.22.0/24NTTCOMNo ROA
202.0.23.0/24NTTCOMNo ROA
202.0.24.0/24NTTCOM, RADBNo ROA
202.0.25.0/24NTTCOMNo ROA
202.0.26.0/24NTTCOMNo ROA
202.0.27.0/24NTTCOMNo ROA
202.0.28.0/22NTTCOM, RADBNo ROA
202.0.28.0/23NTTCOM, RADBNo ROA
202.0.28.0/24NTTCOM, RADBNo ROA
202.0.29.0/24NTTCOM, RADBNo ROA
202.0.30.0/23NTTCOM, RADBNo ROA
202.0.30.0/24NTTCOM, RADBNo ROA
202.0.31.0/24NTTCOM, RADBNo ROA
202.4.0.0/20NTTCOM, RADBNo ROA
202.4.0.0/23NTTCOM, RADBNo ROA
202.4.2.0/23NTTCOM, RADBNo ROA
202.4.4.0/23NTTCOM, RADBNo ROA
202.4.6.0/23NTTCOM, RADBNo ROA
202.4.8.0/21NTTCOM, RADBNo ROA
202.4.8.0/22NTTCOM, RADBNo ROA
202.4.12.0/22NTTCOM, RADBNo ROA
202.4.12.0/23NTTCOM, RADBNo ROA
202.4.12.0/24NTTCOM, RADBNo ROA
202.4.13.0/24NTTCOM, RADBNo ROA
202.4.14.0/23NTTCOM, RADBNo ROA
202.4.14.0/24NTTCOM, RADBNo ROA
202.4.15.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.