bgpreport

Network · data from 2026-11-12

AS24190 SET-AS-TH - The Stock Exchange of Thailand

Registry name: SET-AS-TH - The Stock Exchange of Thailand, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24190, 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.
103.136.252.0/23 No ROA Other IRR onlyRADB 672 100% 68
103.136.252.0/24 No ROA Other IRR onlyRADB 672 100% 68
103.136.253.0/24 No ROA Other IRR onlyRADB 672 100% 68
203.99.252.0/23 No ROA Other IRR onlyNTTCOM, RADB 672 100% 68
203.99.252.0/24 No ROA Other IRR onlyRADB 672 100% 68
203.99.253.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 69
103.71.6.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.71.6.0/23 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
103.71.7.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
119.63.74.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68

AS-SET

AS24190 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 15 are in fix.csv.

  • ROA: none9
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none103.136.252.0/23No ROA covers it. Add a ROA for AS24190, maxLength 23.672 of 673
Route object: RIR103.136.252.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.136.252.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.672 of 673
Route object: RIR103.136.252.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.136.253.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.672 of 673
Route object: RIR103.136.253.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.99.252.0/23No ROA covers it. Add a ROA for AS24190, maxLength 23.672 of 673
Route object: RIR203.99.252.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.99.252.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.672 of 673
Route object: RIR203.99.252.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.99.253.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.672 of 673
Route object: RIR203.99.253.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.71.6.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.672 of 673
ROA: none103.71.6.0/23No ROA covers it. Add a ROA for AS24190, maxLength 23.671 of 673
ROA: none103.71.7.0/24No ROA covers it. Add a ROA for AS24190, maxLength 24.671 of 673

Route objects not announced

Every route object with origin AS24190 is announced.

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.