bgpreport

Network · data from 2026-11-12

AS38322 Packet-One Networks

Registry name: TTSSB-MY - TM TECHNOLOGY SERVICES SDN. BHD., MY · PeeringDB

27IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
110Route objects not announced registered with origin AS38322, seen from no peer

Announced routes

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

122.255.96.0/19 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
42.153.16.0/24 Valid RIR databaseAPNIC 671 100% 67
42.153.19.0/24 Valid RIR databaseAPNIC 671 100% 67
42.153.24.0/24 Valid RIR databaseAPNIC 671 100% 67
42.153.25.0/24 Valid RIR databaseAPNIC 671 100% 67
42.153.20.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.21.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.22.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.23.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.26.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.89.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.128.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.129.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.130.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.131.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.132.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.133.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.134.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.135.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.136.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.137.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.138.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.139.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.140.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.141.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.142.0/24 Valid RIR databaseAPNIC 668 99% 67
42.153.143.0/24 Valid RIR databaseAPNIC 668 99% 67
2401:3c00:c0::/46 Valid RIR databaseAPNIC 636 100% 69
2401:3c00:dc::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS38322's PeeringDB record names no 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 110 are in fix.csv.

  • Route object: not announced110

Route objects not announced

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

42.152.0.0/14APNICValid
42.153.4.0/24APNICValid
42.153.6.0/24APNICValid
42.153.7.0/24APNICValid
42.153.8.0/24APNICValid
42.153.9.0/24APNICValid
42.153.10.0/24APNICValid
42.153.11.0/24APNICValid
42.153.28.0/24APNICValid
42.153.29.0/24APNICValid
42.153.32.0/24APNICValid
42.153.33.0/24APNICValid
42.153.34.0/24APNICValid
42.153.35.0/24APNICValid
42.153.36.0/24APNICValid
42.153.37.0/24APNICValid
42.153.38.0/24APNICValid
42.153.39.0/24APNICValid
42.153.40.0/24APNICValid
42.153.41.0/24APNICValid
42.153.42.0/24APNICValid
42.153.43.0/24APNICValid
42.153.44.0/24APNICValid
42.153.45.0/24APNICValid
42.153.46.0/24APNICValid
42.153.47.0/24APNICValid
42.153.48.0/24APNICValid
42.153.49.0/24APNICValid
42.153.50.0/24APNICValid
42.153.51.0/24APNICValid
42.153.52.0/24APNICValid
42.153.53.0/24APNICValid
42.153.54.0/24APNICValid
42.153.55.0/24APNICValid
42.153.56.0/24APNICValid
42.153.57.0/24APNICValid
42.153.58.0/24APNICValid
42.153.59.0/24APNICValid
42.153.60.0/24APNICValid
42.153.61.0/24APNICValid
42.153.62.0/24APNICValid
42.153.63.0/24APNICValid
42.153.95.0/24APNICValid
42.153.96.0/24APNICValid
42.153.144.0/24APNICValid
42.153.145.0/24APNICValid
42.153.146.0/24APNICValid
42.153.147.0/24APNICValid
42.153.148.0/24APNICValid
42.153.149.0/24APNICValid
42.153.150.0/24APNICValid
42.153.151.0/24APNICValid
42.153.152.0/24APNICValid
42.153.153.0/24APNICValid
42.153.154.0/24APNICValid
42.153.155.0/24APNICValid
42.153.156.0/24APNICValid
42.153.157.0/24APNICValid
42.153.158.0/24APNICValid
42.153.159.0/24APNICValid
120.139.0.0/16NTTCOMNo ROA
120.139.224.0/19NTTCOMNo ROA
120.139.254.0/24RADBNo ROA
120.140.0.0/19APNICInvalid: origin
120.140.32.0/19APNICInvalid: origin
2401:3c00:8::/46APNICValid
2401:3c00:14::/46APNICValid
2401:3c00:18::/46APNICValid
2401:3c00:48::/46APNICValid
2401:3c00:54::/46APNICValid
2401:3c00:58::/46APNICValid
2401:3c00:a4::/48APNICValid
2401:3c00:a5::/48APNICValid
2401:3c00:a6::/48APNICValid
2401:3c00:a7::/48APNICValid
2401:3c00:a8::/48APNICValid
2401:3c00:a9::/48APNICValid
2401:3c00:c0:5::/64APNICValid
2401:3c00:d8::/48APNICValid
2401:3c00:d9::/48APNICValid
2401:3c00:da::/48APNICValid
2401:3c00:db::/48APNICValid
2401:3c00:100::/43APNICValid
2401:3c00:120::/43APNICValid
2401:3c00:180::/43APNICValid
2401:3c00:1a0::/43APNICValid
2401:3c00:260::/48APNICValid
2401:3c00:261::/48APNICValid
2401:3c00:262::/48APNICValid
2401:3c00:280::/48APNICValid
2401:3c00:281::/48APNICValid
2401:3c00:290::/48APNICValid
2401:3c00:291::/48APNICValid
2401:3c00:292::/48APNICValid
2401:3c00:293::/48APNICValid
2401:3c00:294::/48APNICValid
2401:3c00:295::/48APNICValid
2401:3c00:2a0::/48APNICValid
2401:3c00:2a1::/48APNICValid
2401:3c00:2a2::/48APNICValid
2401:3c00:2a3::/48APNICValid
2401:3c00:2a4::/48APNICValid
2401:3c00:2a5::/48APNICValid
2401:3c00:2b0::/48APNICValid
2401:3c00:2b1::/48APNICValid
2401:3c00:2b2::/48APNICValid
2401:3c00:2b3::/48APNICValid
2401:3c00:2b4::/48APNICValid
2401:3c00:2b5::/48APNICValid
2401:3c00:2c0::/42APNICValid

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.