Network · data from 2026-11-12
AS134095 ITMX-AS - National ITMX Company Limited
Registry name: ITMX-AS - National ITMX Company Limited, TH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS134095, 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.
| 14.207.226.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 110.170.238.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 110.170.137.0/24 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 210.86.152.0/24 | Valid | RIR databaseAPNIC, RADB | 668 99% |
| 110.170.147.0/24 | Valid | RIR databaseAPNIC, RADB | 667 99% |
AS-SET
AS134095 isn't in PeeringDB, where networks name their AS-SET.
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 AS134095 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.