Trello deactivated my account even though I am not Russia/Belarus-based.

Hazel_yk4ovm

Atlassian sent me an email that landed in my spam folder unfortunately. It reads the following:

"We are contacting you to let you know that Atlassian is winding down its operations in Russia and Belarus, and our records identify you are using Atlassian's no‑charge product(s) within these identified regions. As such, this email constitutes notice that, in accordance with our Cloud Terms of Service, we will terminate your Atlassian account in 30 days."

However, I am based in the US and have never used a Russia-based VPN or anything like that while using Trello, so I am not sure why my account was marked as being from these countries.

I've been forced to create a new account just to access my Trello boards as I use them daily for work - this is the account I'm using to create this discussion. I have been using Trello since 2016, well before they fell under the Atlassian umbrella.

I created a ticket with Atlassian, but I have no idea how long it will take to get back my account.

Is anyone else going through this who's account was wrongly flagged? Is there a number I can all since the support response times are taking forever?

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

I am sorry this has happened.  I can give you a bit of an explanation, but it's not going to be ideal or explain exactly why you have been hit.

There are a lot of accounts for Atlassian to look at.  There's no chance a team of humans could verify every account, so obviously, there is a huge amount of automation of the shut-down process, and although Atlassian have mostly done a good job of identifying accounts that have been forced to support the illegal invasion of Ukraine, the process is not perfect.  There are both false negatives and false positives.

From what you've said, you have been flagged as a false positive (probably just that your email address on your account looks like it is provided by an organisation that Russian law has forced to support the invasion)

You have done the right thing - a support call, and temporary access via a non-sanctoned new account.  

But all you can do is wait for the support call to be processed.  You're not alone here, there are other false-positives I know of, and I know Atlassian do get them fixed, but it is not quick, there's a lot of support to do!

I've asked Atlassian to move yours higher on the to-do list, as you've asked here, but I can't tell you how long it might take. 

Just to help out, I would, if it were private, ask for the domain of your email on your Atlassian account, but in public, I don't want to get you added to any spam lists.  Atlassian can see your domain on your Atlassian account though, so can you confirm that the account you used to post this question is on the same as the blocked account?  Or at least that they are both on the same domain?