bgpreport

Network · data from 2026-11-12

AS37992 THAMMASAT-BORDER-AS - Thammasat University in thailand

Registry name: THAMMASAT-BORDER-AS - Thammasat University in thailand, TH · not in PeeringDB

34IPv4 routes 64.7% RPKI valid · 100.0% with a route object
10IPv6 routes 20.0% RPKI valid · 30.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
20No ROA 7 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS37992, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS37992, 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:140:1::/48 No ROA Nonecovered by 2404:140::/32 5 1%low visibility 4
2404:140:a00::/40 No ROA Nonecovered by 2404:140::/32 5 1%low visibility 4
2404:140:1000::/36 No ROA Nonecovered by 2404:140::/32 5 1%low visibility 4
2404:140:f000::/38 No ROA Nonecovered by 2404:140::/32 5 1%low visibility 4
2404:140:1:1::/64 No ROA Nonecovered by 2404:140::/32 1 0%low visibility 1
2404:140:1:35::/64 No ROA Nonecovered by 2404:140::/32 1 0%low visibility 1
2404:140:21:1::/64 No ROA Nonecovered by 2404:140::/32 1 0%low visibility 1
192.150.249.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 69
203.131.208.0/20 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.131.216.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.131.218.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.131.220.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.131.222.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
203.131.223.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.131.208.0/23 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
203.131.210.0/23 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
203.131.212.0/23 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
203.131.214.0/23 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
2404:140::/32 No ROA Other IRR onlyRADB 631 99% 70
203.131.216.0/24 No ROA Other IRR onlyRADB 1 0%low visibility 1
61.90.234.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
61.90.235.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
61.90.236.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
61.90.237.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
119.46.188.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
119.46.189.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
119.46.235.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
202.28.88.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.89.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.90.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.91.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
110.164.61.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
110.164.62.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
110.164.83.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
110.164.84.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
110.164.178.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
110.164.179.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
119.46.236.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
119.46.238.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
2001:fb0:100e::/48 Valid RIR databaseAPNIC, RADB 631 99% 70
2001:fb0:100f::/48 Valid RIR databaseAPNIC, RADB 631 99% 70
119.46.190.0/24 Valid RIR databaseAPNIC, RADB 143 21% 51
119.46.191.0/24 Valid RIR databaseAPNIC, RADB 143 21% 51
119.46.237.0/24 Valid RIR databaseAPNIC, RADB 143 21% 51

AS-SET

AS37992 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 56 are in fix.csv.

  • ROA: none20
  • Route object: none7
  • Route object: RIR13
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none2404:140:1::/48No ROA covers it. Add a ROA for AS37992, maxLength 48.5 of 636
Route object: none2404:140:1::/48No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37992 in the RIR database for the space.5 of 636
ROA: none2404:140:a00::/40No ROA covers it. Add a ROA for AS37992, maxLength 40.5 of 636
Route object: none2404:140:a00::/40No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37992 in the RIR database for the space.5 of 636
ROA: none2404:140:1000::/36No ROA covers it. Add a ROA for AS37992, maxLength 36.5 of 636
Route object: none2404:140:1000::/36No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37992 in the RIR database for the space.5 of 636
ROA: none2404:140:f000::/38No ROA covers it. Add a ROA for AS37992, maxLength 38.5 of 636
Route object: none2404:140:f000::/38No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37992 in the RIR database for the space.5 of 636
ROA: none2404:140:1:1::/64No ROA covers it. Add a ROA for AS37992, maxLength 64.1 of 636
Route object: none2404:140:1:1::/64No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS37992 in the RIR database for the space.1 of 636
ROA: none2404:140:1:35::/64No ROA covers it. Add a ROA for AS37992, maxLength 64.1 of 636
Route object: none2404:140:1:35::/64No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS37992 in the RIR database for the space.1 of 636
ROA: none2404:140:21:1::/64No ROA covers it. Add a ROA for AS37992, maxLength 64.1 of 636
Route object: none2404:140:21:1::/64No route object for it. A route object for 2404:140::/32 with origin AS37992 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS37992 in the RIR database for the space.1 of 636
ROA: none192.150.249.0/24No ROA covers it. Add a ROA for AS37992, maxLength 24.673 of 673
Route object: RIR192.150.249.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.208.0/20No ROA covers it. Add a ROA for AS37992, maxLength 20.673 of 673
Route object: RIR203.131.208.0/20Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.216.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.673 of 673
Route object: RIR203.131.216.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.218.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.673 of 673
Route object: RIR203.131.218.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.220.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.673 of 673
Route object: RIR203.131.220.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.222.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.673 of 673
Route object: RIR203.131.222.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.223.0/24No ROA covers it. Add a ROA for AS37992, maxLength 24.673 of 673
Route object: RIR203.131.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.131.208.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.670 of 673
Route object: RIR203.131.208.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.131.210.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.670 of 673
Route object: RIR203.131.210.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.131.212.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.670 of 673
Route object: RIR203.131.212.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.131.214.0/23No ROA covers it. Add a ROA for AS37992, maxLength 23.670 of 673
Route object: RIR203.131.214.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none2404:140::/32No ROA covers it. Add a ROA for AS37992, maxLength 32.631 of 636
Route object: RIR2404:140::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none203.131.216.0/24No ROA covers it. Add a ROA for AS37992, maxLength 24.1 of 673
Route object: RIR203.131.216.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

202.28.88.0/22RADBNo ROA
202.131.208.0/23RADBNo ROA
203.131.208.0/24RADBNo ROA
203.131.209.0/24RADBNo ROA
203.131.210.0/24RADBNo ROA
203.131.211.0/24RADBNo ROA
203.131.212.0/24RADBNo ROA
203.131.213.0/24RADBNo ROA
203.131.214.0/24RADBNo ROA
203.131.215.0/24RADBNo ROA
203.131.217.0/24RADBNo ROA
203.131.218.0/24RADBNo ROA
203.131.219.0/24RADBNo ROA
203.131.220.0/24RADBNo ROA
203.131.221.0/24RADBNo ROA
203.131.222.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.