bgpreport

Network · data from 2026-11-12

AS9562 MSU-TH-AP - Mahasarakham University

Registry name: MSU-TH-AP - Mahasarakham University, TH · not in PeeringDB

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

Announced routes

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

202.28.32.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.33.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.34.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.28.35.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
2001:3c8:a701::/48 Valid RIR databaseAPNIC, RADB 636 100% 70

AS-SET

AS9562 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

58.147.84.0/22RADBNo ROA
58.147.84.0/24RADBNo ROA
58.147.85.0/24RADBNo ROA
58.147.86.0/24RADBNo ROA
58.147.87.0/24RADBNo ROA
202.28.32.0/22NTTCOM, RADBNo ROA
202.28.32.0/23NTTCOM, RADBNo ROA
202.28.34.0/23NTTCOM, RADBNo ROA
203.153.188.0/22RADBNo ROA
203.153.188.0/24RADBNo ROA
203.153.189.0/24RADBNo ROA
203.153.190.0/24RADBNo ROA
203.153.191.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.