Data residency - can pinned location cause performance issues?

[Nina K]

If data is pinned to the US location however, it's global firm and have a good number of folks in Asia. Can this cause performance issues for people accessing via Asia?

[Luis Machado · Accepted solution]

Hi @Nina K 

The short answer is yes.

The nature of data residency is such that the data is physically stored in whatever geographic location it needs to be in (like for GDPR compliance).

Normally Atlassian cloud leverages edge locations to help with latency so that the data is accessed closer to where it's being requested from. If you pin your data to a specific location then users will be subject to the physical distance the data has to travel to be served to them and can potentially have higher latency that will feel like a performance impact.

Here's a link to Atlassian's documentation on data residency: https://www.atlassian.com/software/data-residency

And this one has information about how the cloud architecture is structured: https://www.atlassian.com/trust/reliability/cloud-architecture-and-operational-practices#cloud-infrastructure

Hope this helps!

[Nina K]

Thank you!

[Trudy Claspill]

Hello @Nina K 

Welcome to the community.

Do you have your data pinned currently? Or are you asking this question to help you decide if you should pin your data?

If it is already pinned, are you users in Asia experiencing performance issue not seen by your users in the US?

[Nina K]

Thanks for replying got the answer!