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
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% |
| 106.0.128.0/18 | No ROA | Nonecovered by 106.0.128.0/17 | 670 100% |
| 182.93.128.0/18 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 202.143.128.0/18 | No ROA | Other IRR onlyRADB | 670 100% |
| 203.172.128.0/17 | No ROA | Other IRR onlyRADB | 670 100% |
| 101.51.0.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 101.51.16.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 101.51.152.0/21 | Valid | RIR databaseAPNIC | 672 100% |
| 182.52.230.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 1.0.197.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 1.10.135.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 101.108.48.0/21 | Valid | RIR databaseAPNIC | 671 100% |
| 118.172.153.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 101.51.64.0/22 | Valid | RIR databaseAPNIC | 670 100% |
| 101.51.176.0/21 | Valid | RIR databaseAPNIC | 670 100% |
| 113.53.1.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 113.53.64.0/20 | Valid | RIR databaseAPNIC | 670 100% |
| 125.27.24.0/21 | Valid | RIR databaseAPNIC | 670 100% |
| 125.27.192.0/21 | Valid | RIR databaseAPNIC | 670 100% |
| 125.27.208.0/20 | Valid | RIR databaseAPNIC | 670 100% |
| 125.27.240.0/22 | Valid | RIR databaseAPNIC | 670 100% |
| 182.52.160.0/20 | Valid | RIR databaseAPNIC | 670 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 1.20.247.0/24 | No ROA covers it. Add a ROA for AS23974, maxLength 24. |
| Route object: none | 1.20.247.0/24 | Route objects for it name AS9737, AS23969. Add a route object with origin AS23974 in the RIR database for the space. |
| ROA: none | 106.0.128.0/18 | No ROA covers it. Add a ROA for AS23974, maxLength 18. |
| Route object: none | 106.0.128.0/18 | No 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. |
| ROA: none | 182.93.128.0/18 | No ROA covers it. Add a ROA for AS23974, maxLength 18. |
| Route object: RIR | 182.93.128.0/18 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 202.143.128.0/18 | No ROA covers it. Add a ROA for AS23974, maxLength 18. |
| Route object: RIR | 202.143.128.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.172.128.0/17 | No ROA covers it. Add a ROA for AS23974, maxLength 17. |
| Route object: RIR | 203.172.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
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/17 | RADB | No ROA |
| 182.93.128.0/17 | NTTCOM, RADB | No ROA |
| 182.93.128.0/19 | NTTCOM, RADB | No ROA |
| 182.93.128.0/20 | NTTCOM, RADB | No ROA |
| 182.93.128.0/21 | NTTCOM, RADB | No ROA |
| 182.93.128.0/22 | NTTCOM, RADB | No ROA |
| 182.93.128.0/23 | NTTCOM, RADB | No ROA |
| 182.93.128.0/24 | NTTCOM, RADB | No ROA |
| 182.93.144.0/21 | RADB | No ROA |
| 182.93.152.0/21 | RADB | No ROA |
| 182.93.160.0/21 | RADB | No ROA |
| 182.93.172.0/23 | RADB | No ROA |
| 182.93.177.0/24 | RADB | No ROA |
| 182.93.178.0/24 | RADB | No ROA |
| 202.143.128.0/19 | NTTCOM, RADB | No ROA |
| 202.143.128.0/20 | NTTCOM, RADB | No ROA |
| 202.143.128.0/21 | NTTCOM, RADB | No ROA |
| 202.143.128.0/22 | NTTCOM, RADB | No ROA |
| 202.143.128.0/23 | NTTCOM, RADB | No ROA |
| 202.143.128.0/24 | NTTCOM, RADB | No ROA |
| 202.143.132.0/22 | RADB | No ROA |
| 202.143.136.0/22 | RADB | No ROA |
| 202.143.140.0/22 | RADB | No ROA |
| 202.143.144.0/20 | RADB | No ROA |
| 202.143.144.0/22 | RADB | No ROA |
| 202.143.148.0/22 | RADB | No ROA |
| 202.143.152.0/22 | RADB | No ROA |
| 202.143.156.0/22 | RADB | No ROA |
| 202.143.160.0/19 | NTTCOM, RADB | No ROA |
| 202.143.160.0/20 | NTTCOM, RADB | No ROA |
| 202.143.160.0/21 | NTTCOM, RADB | No ROA |
| 202.143.160.0/22 | NTTCOM, RADB | No ROA |
| 202.143.160.0/23 | NTTCOM, RADB | No ROA |
| 202.143.160.0/24 | NTTCOM, RADB | No ROA |
| 202.143.164.0/22 | RADB | No ROA |
| 202.143.168.0/22 | RADB | No ROA |
| 202.143.172.0/22 | RADB | No ROA |
| 202.143.176.0/20 | RADB | No ROA |
| 202.143.180.0/22 | RADB | No ROA |
| 202.143.188.0/22 | RADB | No ROA |
| 203.172.128.0/18 | NTTCOM, RADB | No ROA |
| 203.172.128.0/19 | NTTCOM, RADB | No ROA |
| 203.172.128.0/20 | NTTCOM, RADB | No ROA |
| 203.172.128.0/21 | NTTCOM, RADB | No ROA |
| 203.172.128.0/22 | NTTCOM, RADB | No ROA |
| 203.172.128.0/23 | NTTCOM, RADB | No ROA |
| 203.172.128.0/24 | NTTCOM, RADB | No ROA |
| 203.172.132.0/22 | RADB | No ROA |
| 203.172.140.0/22 | RADB | No ROA |
| 203.172.148.0/22 | RADB | No ROA |
| 203.172.156.0/22 | RADB | No ROA |
| 203.172.160.0/19 | RADB | No ROA |
| 203.172.164.0/22 | RADB | No ROA |
| 203.172.192.0/18 | NTTCOM, RADB | No ROA |
| 203.172.192.0/19 | NTTCOM, RADB | No ROA |
| 203.172.192.0/20 | NTTCOM, RADB | No ROA |
| 203.172.192.0/21 | NTTCOM, RADB | No ROA |
| 203.172.192.0/22 | NTTCOM, RADB | No ROA |
| 203.172.192.0/23 | NTTCOM, RADB | No ROA |
| 203.172.192.0/24 | NTTCOM, RADB | No ROA |
| 203.172.224.0/19 | RADB | No ROA |
| 203.172.246.0/24 | RADB | No 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.