bgpreport

Network · data from 2026-11-12

AS9655 TPMNETWORK-AS-AP - TPM Corp. Berhad,

Registry name: TPMNETWORK-AS-AP - TPM Corp. Berhad,, MY · not in PeeringDB

12IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
12No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
22Route objects not announced registered with origin AS9655, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9655, 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.
202.129.160.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.161.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.162.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.163.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.164.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.165.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.166.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.167.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.168.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.173.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.174.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68
202.129.175.0/24 No ROA RIR databaseAPNIC, NTTCOM, RADB 671 100% 68

AS-SET

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

  • ROA: none12
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none202.129.160.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.161.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.162.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.163.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.164.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.165.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.166.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.167.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.168.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.173.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.174.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673
ROA: none202.129.175.0/24No ROA covers it. Add a ROA for AS9655, maxLength 24.671 of 673

Route objects not announced

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

202.129.160.0/20NTTCOM, RADBNo ROA
202.129.160.0/21NTTCOM, RADBNo ROA
202.129.160.0/22NTTCOM, RADBNo ROA
202.129.160.0/23NTTCOM, RADBNo ROA
202.129.162.0/23NTTCOM, RADBNo ROA
202.129.164.0/22NTTCOM, RADBNo ROA
202.129.164.0/23NTTCOM, RADBNo ROA
202.129.166.0/23NTTCOM, RADBNo ROA
202.129.168.0/21NTTCOM, RADBNo ROA
202.129.168.0/22NTTCOM, RADBNo ROA
202.129.168.0/23NTTCOM, RADBNo ROA
202.129.169.0/24APNIC, NTTCOM, RADBNo ROA
202.129.170.0/23NTTCOM, RADBNo ROA
202.129.170.0/24APNIC, NTTCOM, RADBNo ROA
202.129.171.0/24APNIC, NTTCOM, RADBNo ROA
202.129.172.0/22NTTCOM, RADBNo ROA
202.129.172.0/23NTTCOM, RADBNo ROA
202.129.172.0/24APNIC, NTTCOM, RADBNo ROA
202.129.174.0/23NTTCOM, RADBNo ROA
2401:5980::/48APNICNo ROA
2401:5980:a::/48APNICNo ROA
2401:5980:b::/48APNICNo 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.