Network · data from 2026-11-12

AS134166 TOT-IDC-AS-AP - Internet Data Center Service

Registry name: TOT-IDC-AS-AP - Internet Data Center Service, TH · not in PeeringDB

30IPv4 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

7Route objects not announced registered with origin AS134166, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134166, 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.179.246.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
1.179.247.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
113.53.228.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.174.8.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.174.9.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
118.174.10.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.174.11.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.175.1.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.175.24.0/22	Valid	RIR databaseAPNIC, RADB	673 100%	68
118.175.24.0/24	Valid	RIR databaseAPNIC	673 100%	68
118.175.25.0/24	Valid	RIR databaseAPNIC	673 100%	68
118.175.28.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
118.175.94.0/24	Valid	RIR databaseAPNIC	673 100%	68
180.180.243.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
180.180.244.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
180.180.245.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
180.180.247.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.4.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.6.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.8.0/22	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.8.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.14.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.25.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.70.0/24	Valid	RIR databaseAPNIC	673 100%	68
203.113.71.0/24	Valid	RIR databaseAPNIC	673 100%	68
203.113.95.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.113.126.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.114.98.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
203.114.102.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	673 100%	68
180.180.242.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	68
2001:ec0:100::/40	Valid	RIR databaseAPNIC, RADB	635 100%	69

AS-SET

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

Route object: not announced7

Route objects not announced

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


118.175.24.0/23	APNIC	Valid
118.175.26.0/23	APNIC	Valid
118.175.26.0/24	APNIC	Valid
118.175.27.0/24	APNIC	Valid
203.113.7.0/24	RADB	No ROA
203.113.10.0/24	APNIC, NTTCOM, RADB	Valid
203.114.97.0/24	APNIC, RADB	Valid

118.175.24.0/23

APNIC

Valid

118.175.26.0/23

APNIC

Valid

118.175.26.0/24

APNIC

Valid

118.175.27.0/24

APNIC

Valid

203.113.7.0/24

RADB

No ROA

203.113.10.0/24

APNIC, NTTCOM, RADB

Valid

203.114.97.0/24

APNIC, RADB

Valid

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.