Sorry, i haven't server spread across the world.... Not yet
The better i can do is giving these ping results from my server to have an idea of the geographical distance:
--- blockchain.info ping statistics ---
34 packets transmitted, 34 received, 0% packet loss, time 33054ms
rtt min/avg/max/mdev = 16.583/16.696/16.777/0.145 ms
--- btc.blockr.io ping statistics ---
40 packets transmitted, 40 received, 0% packet loss, time 39067ms
rtt min/avg/max/mdev = 17.946/18.102/18.328/0.181 ms
--- api.blockcypher.com ping statistics ---
320 packets transmitted, 320 received, 0% packet loss, time 319474ms
rtt min/avg/max/mdev = 20.980/21.693/22.470/0.425 ms
--- blockexplorer.com ping statistics ---
331 packets transmitted, 331 received, 0% packet loss, time 330548ms
rtt min/avg/max/mdev = 16.664/16.832/17.010/0.102 ms
--- api.biteasy.com ping statistics ---
38 packets transmitted, 38 received, 0% packet loss, time 55960ms
rtt min/avg/max/mdev = 16.750/16.966/20.020/0.547 ms
--- api.chain.com ping statistics ---
39 packets transmitted, 30 received, 23% packet loss, time 46887ms
rtt min/avg/max/mdev = 56.758/57.832/58.737/0.640 ms
--- helloblock-ssl.herokuapp.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4031ms
PING DISABLED
The code and the server are the same for every endpoints so it's not really relevant to the test.
I can say that HTTP Request are made from a thread pool so they are not waiting each other.