Network · data from 2026-11-12

AS9411 NontriNet

Registry name: NONTRINET-AS-AP - Kasetsart University, Thailand, TH · PeeringDB

18IPv4 routes 100.0% RPKI valid · 100.0% with a route object

18IPv6 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

0Route objects not announced registered with origin AS9411, seen from no peer

Announced routes

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


158.108.0.0/16	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.0.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.16.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.32.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.48.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.64.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.80.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.96.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.112.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.128.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.144.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.160.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.176.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.192.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.208.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.224.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
158.108.240.0/20	Valid	RIR databaseAPNIC, RADB	673 100%	69
192.102.83.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	69
2001:3c8:1303::/48	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100::/32	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:1000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:2000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:3000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:4000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:5000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:6000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:7000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:8000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:9000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:a000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:b000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:c000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:d000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:e000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70
2406:3100:f000::/36	Valid	RIR databaseAPNIC, RADB	636 100%	70

AS-SET

PeeringDB's irr_as_set for AS9411: APNIC::AS9411:AS-CORE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS9411 isn't in the set, or no route object for AS9411 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS9411 in it	Not covered
APNIC::AS9411:AS-CORE	APNIC	1	1	36	Yes	0

Name

Database

ASNs

Sets

Route objects

AS9411 in it

Not covered

APNIC::AS9411:AS-CORE

APNIC

Yes

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS9411 is announced.

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.