bgpreport

Network · data from 2026-11-12

AS23974 MOE-AS-AP - Ministry of education

Registry name: MOE-AS-AP - Ministry of education, TH · not in PeeringDB

22IPv4 routes 77.3% RPKI valid · 90.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
62Route objects not announced registered with origin AS23974, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS23974, 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.

1.20.247.0/24 No ROA Other origin only 671 100% 67
106.0.128.0/18 No ROA Nonecovered by 106.0.128.0/17 670 100% 66
182.93.128.0/18 No ROA Other IRR onlyNTTCOM, RADB 670 100% 68
202.143.128.0/18 No ROA Other IRR onlyRADB 670 100% 68
203.172.128.0/17 No ROA Other IRR onlyRADB 670 100% 68
101.51.0.0/20 Valid RIR databaseAPNIC 672 100% 68
101.51.16.0/21 Valid RIR databaseAPNIC 672 100% 68
101.51.152.0/21 Valid RIR databaseAPNIC 672 100% 68
182.52.230.0/24 Valid RIR databaseAPNIC 672 100% 66
1.0.197.0/24 Valid RIR databaseAPNIC 671 100% 68
1.10.135.0/24 Valid RIR databaseAPNIC 671 100% 68
101.108.48.0/21 Valid RIR databaseAPNIC 671 100% 68
118.172.153.0/24 Valid RIR databaseAPNIC 671 100% 66
101.51.64.0/22 Valid RIR databaseAPNIC 670 100% 68
101.51.176.0/21 Valid RIR databaseAPNIC 670 100% 68
113.53.1.0/24 Valid RIR databaseAPNIC 670 100% 68
113.53.64.0/20 Valid RIR databaseAPNIC 670 100% 68
125.27.24.0/21 Valid RIR databaseAPNIC 670 100% 66
125.27.192.0/21 Valid RIR databaseAPNIC 670 100% 66
125.27.208.0/20 Valid RIR databaseAPNIC 670 100% 66
125.27.240.0/22 Valid RIR databaseAPNIC 670 100% 66
182.52.160.0/20 Valid RIR databaseAPNIC 670 100% 66

AS-SET

AS23974 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 72 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced62
ChangePrefix or setDetailFull-table peers
ROA: none1.20.247.0/24No ROA covers it. Add a ROA for AS23974, maxLength 24.671 of 673
Route object: none1.20.247.0/24Route objects for it name AS9737, AS23969. Add a route object with origin AS23974 in the RIR database for the space.671 of 673
ROA: none106.0.128.0/18No ROA covers it. Add a ROA for AS23974, maxLength 18.670 of 673
Route object: none106.0.128.0/18No route object for it. A route object for 106.0.128.0/17 with origin AS23974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23974 in the RIR database for the space.670 of 673
ROA: none182.93.128.0/18No ROA covers it. Add a ROA for AS23974, maxLength 18.670 of 673
Route object: RIR182.93.128.0/18Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.143.128.0/18No ROA covers it. Add a ROA for AS23974, maxLength 18.670 of 673
Route object: RIR202.143.128.0/18Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.172.128.0/17No ROA covers it. Add a ROA for AS23974, maxLength 17.670 of 673
Route object: RIR203.172.128.0/17Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

106.0.128.0/17RADBNo ROA
182.93.128.0/17NTTCOM, RADBNo ROA
182.93.128.0/19NTTCOM, RADBNo ROA
182.93.128.0/20NTTCOM, RADBNo ROA
182.93.128.0/21NTTCOM, RADBNo ROA
182.93.128.0/22NTTCOM, RADBNo ROA
182.93.128.0/23NTTCOM, RADBNo ROA
182.93.128.0/24NTTCOM, RADBNo ROA
182.93.144.0/21RADBNo ROA
182.93.152.0/21RADBNo ROA
182.93.160.0/21RADBNo ROA
182.93.172.0/23RADBNo ROA
182.93.177.0/24RADBNo ROA
182.93.178.0/24RADBNo ROA
202.143.128.0/19NTTCOM, RADBNo ROA
202.143.128.0/20NTTCOM, RADBNo ROA
202.143.128.0/21NTTCOM, RADBNo ROA
202.143.128.0/22NTTCOM, RADBNo ROA
202.143.128.0/23NTTCOM, RADBNo ROA
202.143.128.0/24NTTCOM, RADBNo ROA
202.143.132.0/22RADBNo ROA
202.143.136.0/22RADBNo ROA
202.143.140.0/22RADBNo ROA
202.143.144.0/20RADBNo ROA
202.143.144.0/22RADBNo ROA
202.143.148.0/22RADBNo ROA
202.143.152.0/22RADBNo ROA
202.143.156.0/22RADBNo ROA
202.143.160.0/19NTTCOM, RADBNo ROA
202.143.160.0/20NTTCOM, RADBNo ROA
202.143.160.0/21NTTCOM, RADBNo ROA
202.143.160.0/22NTTCOM, RADBNo ROA
202.143.160.0/23NTTCOM, RADBNo ROA
202.143.160.0/24NTTCOM, RADBNo ROA
202.143.164.0/22RADBNo ROA
202.143.168.0/22RADBNo ROA
202.143.172.0/22RADBNo ROA
202.143.176.0/20RADBNo ROA
202.143.180.0/22RADBNo ROA
202.143.188.0/22RADBNo ROA
203.172.128.0/18NTTCOM, RADBNo ROA
203.172.128.0/19NTTCOM, RADBNo ROA
203.172.128.0/20NTTCOM, RADBNo ROA
203.172.128.0/21NTTCOM, RADBNo ROA
203.172.128.0/22NTTCOM, RADBNo ROA
203.172.128.0/23NTTCOM, RADBNo ROA
203.172.128.0/24NTTCOM, RADBNo ROA
203.172.132.0/22RADBNo ROA
203.172.140.0/22RADBNo ROA
203.172.148.0/22RADBNo ROA
203.172.156.0/22RADBNo ROA
203.172.160.0/19RADBNo ROA
203.172.164.0/22RADBNo ROA
203.172.192.0/18NTTCOM, RADBNo ROA
203.172.192.0/19NTTCOM, RADBNo ROA
203.172.192.0/20NTTCOM, RADBNo ROA
203.172.192.0/21NTTCOM, RADBNo ROA
203.172.192.0/22NTTCOM, RADBNo ROA
203.172.192.0/23NTTCOM, RADBNo ROA
203.172.192.0/24NTTCOM, RADBNo ROA
203.172.224.0/19RADBNo ROA
203.172.246.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.