Can Fly add regional IP in hkg?

1

Access from Mainland China will now be routed to the lax, increasing the latency by two times across the Pacific Ocean.

I understand that optimizing anycast for Mainland China is difficult, can Fly add hkg regional IP so that applications that need it can be explicitly routed to hkg?

References:

3

regional IPs are now available for hkg. please note it’s entirely possible you could still get routed to the US and back; I would be happy to hear that’s not the case though.

1 Like
4

Thanks for the reply!

I did some testing and found that regional IP is slower than shared IP. Traceroute shows that it goes to Japan and then to Hong Kong.

 5  218.65.150.249 (218.65.150.249)  9.793 ms
    222.217.173.73 (222.217.173.73)  9.598 ms
    113.16.236.201 (113.16.236.201)  10.300 ms
 6  202.97.30.173 (202.97.30.173)  21.884 ms
    202.97.81.185 (202.97.81.185)  18.281 ms
    202.97.30.173 (202.97.30.173)  23.484 ms
 7  202.97.93.37 (202.97.93.37)  22.811 ms
    202.97.93.49 (202.97.93.49)  22.695 ms
    202.97.93.57 (202.97.93.57)  22.673 ms
 8  202.97.65.57 (202.97.65.57)  22.277 ms
    202.97.65.61 (202.97.65.61)  19.188 ms
    202.97.91.190 (202.97.91.190)  24.899 ms
 9  203.86.97.18 (203.86.97.18)  123.165 ms  118.391 ms
    xe-2-5-3-3.a03.tokyjp05.jp.bb.gin.ntt.net (129.250.66.157)  129.177 ms
10  ae-5.r32.tokyjp05.jp.bb.gin.ntt.net (129.250.5.93)  128.653 ms *  129.769 ms
11  * * *
12  ae-20.a01.newthk04.hk.bb.gin.ntt.net (129.250.2.255)  165.488 ms  170.011 ms  164.831 ms
13  203.131.243.30 (203.131.243.30)  265.612 ms  228.252 ms  235.998 ms

It seems that regional IP needs route optimization too.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.