bgpreport

Network · data from 2026-11-12

AS55490 TRUEMOVE-AS-AP - True Move Company Limited

Registry name: TRUEMOVE-AS-AP - True Move Company Limited, TH · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
42Route objects not announced registered with origin AS55490, seen from no peer

Announced routes

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

171.102.140.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
171.102.128.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
171.102.132.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
171.102.128.0/20 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
171.102.136.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67

AS-SET

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

  • Route object: not announced42

Route objects not announced

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

27.55.0.0/16RADBInvalid: origin
27.55.0.0/17RADBInvalid: origin
49.237.0.0/16RADBInvalid: origin
49.237.0.0/17RADBInvalid: origin
49.237.0.0/18RADBInvalid: origin
49.237.64.0/18RADBInvalid: origin
49.237.128.0/17RADBInvalid: origin
49.237.128.0/18RADBInvalid: origin
49.237.192.0/18RADBInvalid: origin
171.102.128.0/21APNIC, NTTCOM, RADBValid
171.102.128.0/23APNIC, NTTCOM, RADBValid
171.102.128.0/24APNIC, NTTCOM, RADBValid
171.102.129.0/24APNIC, NTTCOM, RADBValid
171.102.130.0/23APNIC, NTTCOM, RADBValid
171.102.130.0/24APNIC, NTTCOM, RADBValid
171.102.131.0/24APNIC, NTTCOM, RADBValid
171.102.132.0/23APNIC, NTTCOM, RADBValid
171.102.132.0/24APNIC, NTTCOM, RADBValid
171.102.133.0/24APNIC, NTTCOM, RADBValid
171.102.134.0/23APNIC, NTTCOM, RADBValid
171.102.134.0/24APNIC, NTTCOM, RADBValid
171.102.135.0/24APNIC, NTTCOM, RADBValid
171.102.136.0/21APNIC, NTTCOM, RADBValid
171.102.136.0/23APNIC, NTTCOM, RADBValid
171.102.136.0/24APNIC, NTTCOM, RADBValid
171.102.137.0/24APNIC, NTTCOM, RADBValid
171.102.138.0/23APNIC, NTTCOM, RADBValid
171.102.138.0/24APNIC, NTTCOM, RADBValid
171.102.139.0/24APNIC, NTTCOM, RADBValid
171.102.140.0/23APNIC, NTTCOM, RADBValid
171.102.140.0/24APNIC, NTTCOM, RADBValid
171.102.141.0/24APNIC, NTTCOM, RADBValid
171.102.142.0/23APNIC, NTTCOM, RADBValid
171.102.142.0/24APNIC, NTTCOM, RADBValid
171.102.143.0/24APNIC, NTTCOM, RADBValid
180.214.192.0/19RADBNo ROA
180.214.192.0/20RADBNo ROA
180.214.192.0/22RADBNo ROA
180.214.199.0/24RADBNo ROA
180.214.208.0/21RADBNo ROA
180.214.216.0/22RADBNo ROA
223.24.0.0/16RADBInvalid: origin

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.