Geographical spread of the data

[jammerdan]

@Alexey

Thus it’s statistically would be closest nodes to the customer’s location because of low latency and speed. So, the real limit is only customer’s bandwidth.

This confirms what I am trying to figure out here:

Distribution algorithm for node selection

I had uploaded 2 bigger files: File1 and File2 (Map creation takes a while) Both show that the distribution of pieces is mainly in the Europe and North America region and I am wondering if this is a desired outcome. In terms of redundancy and fast worldwide access, I would have expected a broader distribution. Both files seem to have not a single pieces stored in Australia very few in the Asia/Pacific region anyway. Almost none in Africa and very few again in South America. What is the reaso…

So distribution would favor the uploaders location and will distribute the pieces close to his location.

However for redundancy or for collaboration this might not be favorable. A media professional in USA sharing terabytes of data with a production company in Australia might be better off if the data gets close to the location where it is downloaded.
For redundancy it might be better off for a EU customer when his data gets also uploaded far away from the EU in case of an blackout.
And 3rd as it has something to do with the algorithm, on the other hand a German user from the public sector might be required to make sure that data he uploads will only be stored on nodes that are in the EU region.

So how does the algorithm cater for these situations?