bgpreport

Network · data from 2026-11-12

AS138959 TIIHK-AS - Telekomunikasi Indonesia International (Hong Kong) Limited

Registry name: TIIHK-AS - Telekomunikasi Indonesia International (Hong Kong) Limited, HK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS138959, 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.
154.91.1.0/24 Invalid: origin RIR databaseAFRINIC 77 11% 38
103.26.92.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 66
103.26.94.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 66
38.80.9.0/24 Valid RIR databaseARIN 671 100% 66

AS-SET

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

  • ROA: origin1
  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: origin154.91.1.0/24ROAs covering it name AS17561, not AS138959. If AS138959 should announce it, add a ROA for AS138959.77 of 673
ROA: none103.26.92.0/24No ROA covers it. Add a ROA for AS138959, maxLength 24.672 of 673
ROA: none103.26.94.0/24No ROA covers it. Add a ROA for AS138959, maxLength 24.672 of 673

Route objects not announced

Every route object with origin AS138959 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.