Unable to Login to Launcher and Minecraft.net. Information is correct, second occurance

This is the second report I am making on this. Last time I was directed to the discord for assistance, and they weren't able to help, but the error went away after 48 hours. 

The problem;
Minecraft Launcher and Minecraft.net is failing to accept my login credentials despite them being accurate. (There is no hacking/account sharing). Occasionally I can login to the minecraft launcher after 10+ retries, but once I attempt to join a server, it says invalid login credentials, please close program and start again. 

I could just wait 48 hours and hope the authentication serves resolve what ever issue is going on, however this time it is also affecting my partner's login on their computer, resulting in no one being able to play minecraft. (Their credentials are also not invalid, and can only occasionally temporarily logon to the minecraft java edition, but unable to join any server, even local lan hosted. 

The only joint variable is that we have both purchased minecraft overseas, me in America, them in Japan. I can't even login from my phone via wifi, or through cellular data. We are currently residing in Australia. The reason I think this is the cause is due to a weird message I received during my last issue with this problem (that I reported) that said Minecraft needed to verify my region before unlocking my account. I verified I was in fact authorizing account use through minecraft.net, yet this problem persists. 

I am on a windows, my partner is on a mac. So i don't believe it is caused by differing OS. In the discord the only advice that mods could give was that it could be a VPN issues, however even after unistalling vpn's the problem persisted (so I reinstalled vpn's since I need them). Sure enough even with VPN's on, the problem seemed to disappear after some time. So I am confident that VPN's aren't causing this issue either. 

I hope this information helps, and someone can point me in the right direction. 

UPDATE: This has been marked as resolved, however it is not. Where should I report this error if not here...