bgpreport

Network · data from 2026-11-12

AS9486 KMITL-AP - King Mongkut's Institute of Technology Ladkrabang

Registry name: KMITL-AP - King Mongkut's Institute of Technology Ladkrabang, TH · not in PeeringDB

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

Announced routes

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

161.246.0.0/16 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68

AS-SET

AS9486 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 34 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: none161.246.0.0/16No ROA covers it. Add a ROA for AS9486, maxLength 16.673 of 673
Route object: RIR161.246.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

161.246.0.0/17NTTCOM, RADBNo ROA
161.246.0.0/18NTTCOM, RADBNo ROA
161.246.0.0/19NTTCOM, RADBNo ROA
161.246.0.0/20NTTCOM, RADBNo ROA
161.246.0.0/21NTTCOM, RADBNo ROA
161.246.0.0/22NTTCOM, RADBNo ROA
161.246.0.0/23NTTCOM, RADBNo ROA
161.246.0.0/24NTTCOM, RADBNo ROA
161.246.1.0/24RADBNo ROA
161.246.11.0/24RADBNo ROA
161.246.79.0/24RADBNo ROA
161.246.88.0/24RADBNo ROA
161.246.97.0/24RADBNo ROA
161.246.128.0/17RADBNo ROA
161.246.128.0/18RADBNo ROA
161.246.192.0/18RADBNo ROA
161.246.192.0/19RADBNo ROA
161.246.192.0/21RADBNo ROA
161.246.192.0/24RADBNo ROA
161.246.193.0/24RADBNo ROA
161.246.194.0/24RADBNo ROA
161.246.195.0/24RADBNo ROA
161.246.208.0/21RADBNo ROA
161.246.216.0/21RADBNo ROA
161.246.224.0/19RADBNo ROA
161.246.224.0/21RADBNo ROA
161.246.232.0/21RADBNo ROA
161.246.240.0/21RADBNo ROA
161.246.241.0/24RADBNo ROA
161.246.242.0/24RADBNo ROA
161.246.243.0/24RADBNo ROA
161.246.252.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.