Network · data from 2026-11-12

AS135566 NTPCL-AS-AP - National Telecom Public Company Limited

Registry name: NTPCL-AS-AP - National Telecom Public Company Limited, TH · not in PeeringDB

49IPv4 routes 98.0% RPKI valid · 100.0% with a route object

6IPv6 routes 100.0% RPKI valid · 100.0% with a route object

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

8Route objects not announced registered with origin AS135566, seen from no peer

Announced routes

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


164.115.48.0/24	No ROA	Other IRR onlyRADB	673 100%	68
122.155.26.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
122.155.27.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
141.140.32.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
141.140.33.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.197.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.198.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.199.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.204.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.205.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.208.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.212.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.213.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.215.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.216.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
202.139.217.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.96.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.97.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.98.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.99.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.100.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.105.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.106.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.107.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.108.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.109.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.110.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.111.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.112.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.113.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.114.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.115.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.116.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.117.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.118.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
209.15.119.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
141.140.34.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
141.140.39.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.200.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.201.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.206.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.207.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.209.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.210.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
202.139.211.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
209.15.101.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
209.15.102.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
209.15.103.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
209.15.104.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
2001:c38:90a0::/44	Valid	RIR databaseAPNIC, RADB	636 100%	69
2001:c38:90a9::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69
2001:c38:90aa::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69
2001:c38:90ab::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69
2001:c38:90ae::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69
2001:c38:90af::/48	Valid	RIR databaseAPNIC, RADB	636 100%	69

AS-SET

AS135566 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 10 are in fix.csv.

ROA: none1
Route object: RIR1
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
ROA: none	164.115.48.0/24	No ROA covers it. Add a ROA for AS135566, maxLength 24.	673 of 673
Route object: RIR	164.115.48.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

164.115.48.0/24

No ROA covers it. Add a ROA for AS135566, maxLength 24.

673 of 673

Route object: RIR

164.115.48.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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


141.140.35.0/24	RADB	No ROA
202.139.202.0/24	APNIC, RADB	Valid
202.139.203.0/24	APNIC, RADB	Valid
202.139.214.0/24	RADB	No ROA
209.15.96.0/22	RADB	No ROA
209.15.108.0/22	RADB	No ROA
209.15.112.0/22	RADB	No ROA
209.15.116.0/22	RADB	No ROA

141.140.35.0/24

RADB

No ROA

202.139.202.0/24

APNIC, RADB

Valid

202.139.203.0/24

APNIC, RADB

Valid

202.139.214.0/24

RADB

No ROA

209.15.96.0/22

RADB

No ROA

209.15.108.0/22

RADB

No ROA

209.15.112.0/22

RADB

No ROA

209.15.116.0/22

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.