Traffic Routing Issues: Choosing Farther Paths Instead of Closer Ones

Questions / Help
1

Hi there,

I’m experiencing an issue with the routing of traffic to my deployed machines. All of my machines are located in Hong Kong (HKG), yet when accessing them from both Hong Kong and mainland China, the traffic seems to be routed to farther regions such as Sydney (SYD) or Los Angeles (LAS) before returning to my HKG machines.

This behavior contradicts my understanding of fly.io routing, as I would expect the traffic to reach the nearest HKG edge nodes instead of being routed through distant locations.

I have searched the forum for similar issues, but most discussions are outdated and do not provide effective solutions.

Responses from debug.fly.dev has been provided.

From HK
From HK2083×891 112 KB

From China
From China1071×443 6.84 KB

Any insights or suggestions would be greatly appreciated!

Thank you!

2

こんにちはsunxywさん、
私も同様の問題を経験しました。アジアでの Anycast ブロードキャストに何らかの問題があり、BGP が近くの IP を見つけられず、代わりに遠い場所に転送しているのではないかと思います。私のアプリは日本にありますが、一部のユーザーは米国にリダイレクトされ、他のユーザーはヨーロッパにリダイレクトされていることがわかりました。
これは私が以前に提出した問題です。Is there a problem with the anycast nodes broadcasting in the Asia region?

3

Thanks, I think that was the cause of the problem. I will be following your posts for timely updates. I noticed the last status update was 5 days ago, hopefully they are making progress.

4

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