tursodatabase/turso-cli

"Wrong" recommended default location.

leandergangso opened this issue · 2 comments

I'm in Norway, so I would expect that either London or Frankfurt would be the best/fastest/closes option.

However when I run turso db locations -l I'm shown that ewr is the fastest(default).
Don't know why, but suspect something is not right here.

image

FYI: I know for sure that the (default) location was lhr(London) some weeks back.

@leandergangso can you let me know what you see at https://region.turso.io? The lowest latency is selected by the CLI first, and it could be than London was having issues or slower to respond at the time.

Yhe, is London again. So most likely just some network issues, as you said.