tw3 (Taiwan): Hong Kong hairpin and HK-registered address space

[hsyuts 0]

Measured 2026-10-21 from a residential HiNet connection in Taipei.
WireGuard, port 1637. No leak and no tunnel defect found — exit address
was always the server's and DNS stayed inside the tunnel. Two other
things, though:

1. ROUTING. tw3 (103.230.144.102) is reached from Taipei via Hong Kong:

     220-128-7-106.tpdt-4013.hinet.net         5.8 ms
     ae-14.r28.tkokhk01.hk.bb.gin.ntt.net     55.4 ms   <- Hong Kong
     ae-5.r25.taiptw01.tw.bb.gin.ntt.net      61.1 ms   <- back to Taipei
     103.4.28.1                               60.8 ms

   NTT hands off in Taipei, so the server is clearly there — this looks
   like a missing domestic interconnect with HiNet. It costs the server
   its whole geographic advantage:

     tw3            47-50 ms
     your Tokyo     38 ms  (jp2/jp3/jp4)
     Taipei refs     5 ms  (168.95.1.1, 1.1.1.1)

   A Taipei customer is better off on your Tokyo servers than your
   Taipei one, which seems worth a look regardless of anything below.

2. DISCLOSURE. RDAP for that block:

     103.230.144.0/22   DCNL-HK   country HK
                        Data Center Network Limited, Hong Kong

   versus your Tokyo ranges (37.120.210.0/24, 146.70.76.0/24), both
   M247-LTD-TOKYO, country JP.

   Registering a block in one place and deploying it in another is
   routine, and I'm not suggesting the machine is anywhere but Taipei.
   But customers choosing by jurisdiction are choosing where the
   plaintext endpoint sits and who can be compelled over it, and for
   tw3 that spans two jurisdictions while the listing shows one.
   "Taipei, HK-registered addressing" would have told me everything.

Single vantage, single point in time. Your numbered aliases also rotate
— jp3 gave me two different addresses ten minutes apart — so specific
IPs may differ at your end.