Since I moved the database to WEST, to latency reduced to 0.2ms which is better but atlassian recommande to have a latency below 0.1.
So I keep the ticket open for the time being

As a first iteration, I'll move the database in WEST region, it shouldn't take too long since the mysql database is already georedundant

I think moving Confluence into Azure and using Sendgrid is a very reasonable option, but I'm unsure if the scope of work is small enough.

If that's viable, I say go for it

We could restore the database in the WEST region https://docs.microsoft.com/en-us/azure/mysql/howto-restore-server-cli.
We'll have to stop confluence, restore the database, and update confluence configuration with new database endpoint

There aren't a lot of solution
1) We need a newer mysql server than the previous one in the Osuosl network
2) We move confluence on azure in the same region than the database but it also means that the mail configuration should be moved to sendgrid and we may have other side effect that I don't know at the moment
R. Tyler Croy any thought on this?

Same results between AZURE(WEST2) and WEST

From Azure(WEST2)
1 row in set (0.03 sec)

From previous database (OSUOSL)
mysql> select 1 ;
1 row in set (0.00 sec)

From Azure (EAST2)
mysql> select 1 ;
1 row in set (0.07 sec)