bgpreport

Network · data from 2026-11-12

AS38296 NSTDA-TH-AS-AP - National Science and Technology Development Agency

Registry name: NSTDA-TH-AS-AP - National Science and Technology Development Agency, TH · not in PeeringDB

16IPv4 routes 93.8% RPKI valid · 100.0% with a route object
0IPv6 routes
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
12Route objects not announced registered with origin AS38296, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38296, 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.
203.185.136.0/23 No ROA Other IRR onlyRADB 673 100% 68
203.185.129.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
203.185.130.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.130.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.131.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
203.185.132.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
203.185.132.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
203.185.132.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.185.133.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
203.185.134.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.134.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
203.185.135.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
203.185.144.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.144.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.145.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
203.185.100.0/24 Valid RIR databaseAPNIC 132 20% 49

AS-SET

AS38296 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 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none203.185.136.0/23No ROA covers it. Add a ROA for AS38296, maxLength 23.673 of 673
Route object: RIR203.185.136.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

203.151.104.0/24APNIC, RADBValid
203.151.105.0/24APNIC, RADBValid
203.185.97.0/24APNICValid
203.185.136.0/24APNIC, RADBValid
203.185.137.0/24APNIC, NTTCOM, RADBValid
203.185.138.0/23RADBNo ROA
203.185.138.0/24APNIC, NTTCOM, RADBValid
203.185.139.0/24APNIC, RADBValid
203.185.140.0/24APNICValid
203.185.141.0/24APNICValid
203.185.142.0/24APNICValid
203.185.143.0/24APNICValid

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.