Azure Locality and the IPv4 Issue
As we highlighted here recently with an article regarding the upcoming end of IPv4 address allocations from ICANN, this has become a real issue in the internet as highlighted by a recent issue in the Microsoft Azure cloud.
My US Server is in Brazil?!
With the issue of limited IPv4 address spaces available, Microsoft was left in a challenged position which led them to begin allocating IP addresses to some US hosted Azure application environments using IP address ranges allocated to Brazil.
While this is in line with their policies that data locality does not have to line up with network addressing, it does highlight an upcoming challenge with the use of geo-location services that are using IP addresses to define where your server is meant to be hosted.
This will definitely be something to watch for in the coming months as we see more of this type of situation arise. Let’s just hope that you don’t use your Azure environment to listen to Spotify, or you may be surprised when it tells you it’s not available because you are in South America.