bgpreport

Network · data from 2026-11-12

AS18409 BOT-TH-AS - Bank of Thailand, Bangkok, Thailand

Registry name: BOT-TH-AS - Bank of Thailand, Bangkok, Thailand, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18409, 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.90.4.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
202.90.6.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
202.90.7.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
2404:e680:1140::/48 No ROA Other IRR onlyRADB 636 100% 69
2404:e680::/32 No ROA Other IRR onlyRADB 540 85% 69
2404:e680:1101::/48 No ROA Other IRR onlyRADB 538 85% 69
2404:e680:1120::/48 No ROA Other IRR onlyRADB 538 85% 69

AS-SET

AS18409 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 21 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none202.90.4.0/24No ROA covers it. Add a ROA for AS18409, maxLength 24.672 of 673
Route object: RIR202.90.4.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.90.6.0/24No ROA covers it. Add a ROA for AS18409, maxLength 24.672 of 673
Route object: RIR202.90.6.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none202.90.7.0/24No ROA covers it. Add a ROA for AS18409, maxLength 24.672 of 673
Route object: RIR202.90.7.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2404:e680:1140::/48No ROA covers it. Add a ROA for AS18409, maxLength 48.636 of 636
Route object: RIR2404:e680:1140::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2404:e680::/32No ROA covers it. Add a ROA for AS18409, maxLength 32.540 of 636
Route object: RIR2404:e680::/32Route object only in RADB. Add it in the RIR database for the space.540 of 636
ROA: none2404:e680:1101::/48No ROA covers it. Add a ROA for AS18409, maxLength 48.538 of 636
Route object: RIR2404:e680:1101::/48Route object only in RADB. Add it in the RIR database for the space.538 of 636
ROA: none2404:e680:1120::/48No ROA covers it. Add a ROA for AS18409, maxLength 48.538 of 636
Route object: RIR2404:e680:1120::/48Route object only in RADB. Add it in the RIR database for the space.538 of 636

Route objects not announced

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

202.90.4.0/22NTTCOM, RADBNo ROA
202.90.4.0/23NTTCOM, RADBNo ROA
202.90.5.0/24NTTCOM, RADBNo ROA
202.90.6.0/23NTTCOM, RADBNo ROA
203.129.8.0/21RADBNo ROA
203.129.10.0/24RADBNo ROA
203.129.11.0/24RADBNo 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.