bgpreport

Network · data from 2026-11-12

AS37932 RMUTI-AS-AP - Rajamangala University of Technology Isan

Registry name: RMUTI-AS-AP - Rajamangala University of Technology Isan, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37932, 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.158.192.0/24 No ROA Nonecovered by 203.158.192.0/22 673 100% 67
203.158.193.0/24 No ROA Nonecovered by 203.158.192.0/22 673 100% 67
203.158.194.0/24 No ROA Nonecovered by 203.158.192.0/22 673 100% 67
203.158.207.0/24 No ROA Nonecovered by 203.158.206.0/23 673 100% 67
203.158.195.0/24 No ROA Nonecovered by 203.158.192.0/22 672 100% 67
203.158.192.0/20 No ROA Other IRR onlyRADB 673 100% 69
203.158.196.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.197.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.198.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.158.200.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.201.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.202.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.203.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.204.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.205.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.206.0/24 No ROA Other IRR onlyRADB 673 100% 69
203.158.199.0/24 No ROA Other IRR onlyRADB 672 100% 66
147.50.197.0/24 Valid Other origin only 673 100% 66
147.50.200.0/24 Valid Other origin only 672 100% 66
2001:3c8:c305::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2001:3c8:c10a::/48 Valid RIR databaseAPNIC 322 51% 64
2001:3c8:c109::/48 Valid RIR databaseAPNIC 321 50% 64
2001:3c8:c10b::/48 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS37932 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 42 are in fix.csv.

  • ROA: none17
  • Route object: none7
  • Route object: RIR12
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none203.158.192.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: none203.158.192.0/24No route object for it. A route object for 203.158.192.0/22 with origin AS37932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37932 in the RIR database for the space.673 of 673
ROA: none203.158.193.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: none203.158.193.0/24No route object for it. A route object for 203.158.192.0/22 with origin AS37932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37932 in the RIR database for the space.673 of 673
ROA: none203.158.194.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: none203.158.194.0/24No route object for it. A route object for 203.158.192.0/22 with origin AS37932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37932 in the RIR database for the space.673 of 673
ROA: none203.158.207.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: none203.158.207.0/24No route object for it. A route object for 203.158.206.0/23 with origin AS37932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37932 in the RIR database for the space.673 of 673
ROA: none203.158.195.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.672 of 673
Route object: none203.158.195.0/24No route object for it. A route object for 203.158.192.0/22 with origin AS37932 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37932 in the RIR database for the space.672 of 673
ROA: none203.158.192.0/20No ROA covers it. Add a ROA for AS37932, maxLength 20.673 of 673
Route object: RIR203.158.192.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.196.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.197.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.197.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.198.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.200.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.200.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.201.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.202.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.202.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.203.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.204.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.204.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.205.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.206.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.673 of 673
Route object: RIR203.158.206.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.158.199.0/24No ROA covers it. Add a ROA for AS37932, maxLength 24.672 of 673
Route object: RIR203.158.199.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none147.50.197.0/24Route objects for it name AS45458. Add a route object with origin AS37932 in the RIR database for the space.673 of 673
Route object: none147.50.200.0/24Route objects for it name AS45458. Add a route object with origin AS37932 in the RIR database for the space.672 of 673

Route objects not announced

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

203.158.192.0/22RADBNo ROA
203.158.196.0/23RADBNo ROA
203.158.198.0/23RADBNo ROA
203.158.200.0/22RADBNo ROA
203.158.204.0/23RADBNo ROA
203.158.206.0/23RADBNo 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.