AWS Asia Pacific (Mumbai) Region
aws.amazon.com
aws.amazon.com
You can check my comments on this recent thread for a somewhat more detailed account of my observations:
https://azure.microsoft.com/en-us/regions/
This completely confirms the region as a technological hub moving forward.
India is Microsoft tech heavy (things change though).
Funny story. A few years back, I got a call from one of their Azure BizDev reps. I told them I was happy they supported Linux and the guy wanted to hang up so fast...lol!
Also, Azure India regions are not generally available:
"The India regions are available to volume licensing customers and partners with a local enrollment in India. The India regions will open to direct online Azure subscriptions in 2016."
GCE on the other hand has a very nice interface.
US-East is the cheapest one and it seems to be the one everybody picks first. I can only guess how the capacity there compares to other datacenters
Also you can expect higher costs for hardware and infrastructure in places like India and Brazil
Northern Virginia and Oregon have (generally) cheap power and cheap connectivity to anywhere in the world, with plenty of peering opportunities. In a developing country or with more expensive infrastructure (Mumbai, Tokyo) costs will be higher to get power and pull in fiber to peering locations with enough capacity to supply a provider of Amazon's size.
And maybe its time for the Asia region to be broken away from Pacific (but keep both). Mumbai associated with Pacific introduces dissonance.
Basically, while you can power-up a server in a datacenter, it shouldn't be accessed publicly via DNS. https://en.wikipedia.org/wiki/ICP_license
To me it makes no sense to lump such a huge area together under "asia-pacific" though. Even just Asia would be too big.
I guess your model\map might, so perhaps with these tools you can get insight into your question.
https://bfi.org/about-fuller/big-ideas/dymaxion-world/dymaxi...
I am on a industrial connection and I only faced two failure power cuts in this year and I live in a major Indian city.
Every data center keeps on site generators to deal with power shortages. I think its part of the standard design paradigm (world wide).
Mumbai has stable power whereas in Delhi brownouts are relatively common occurrences.
Its kinda funny to have this pop up anywhere on HN.
http://www.smh.com.au/technology/technology-news/web-chaos-m...
I am sure a DC like this will be able to manage in India :)
6 39 ms 39 ms 39 ms ix-xe-9-0-1-0.tcore2.MLV-Mumbai.as6453.net [180.87.39.57]
7 40 ms 39 ms 39 ms if-ae-2-2.tcore1.MLV-Mumbai.as6453.net [180.87.38.1]
8 131 ms 123 ms 124 ms 180.87.38.6
9 141 ms 135 ms 134 ms 115.114.89.118.static-Mumbai.vsnl.net.in [115.114.89.118]
10 143 ms 136 ms 183 ms 52.95.66.176
11 139 ms 136 ms 136 ms 52.95.66.197
12 124 ms 124 ms 123 ms 52.95.67.208
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 136 ms 136 ms 136 ms <Instance IP>
Whereas for Singapore: 6 145 ms 154 ms 146 ms 38895.sgw.equinix.com [27.111.228.215]
7 94 ms 102 ms 92 ms 52.93.8.10
8 94 ms 92 ms 92 ms 52.93.8.29
9 106 ms 104 ms 104 ms 203.83.223.31
10 107 ms 104 ms 104 ms <Instance IP> server-54-230-174-13.bom2.r.cloudfront.net
btw 70 ms avg ping from LK, not badFrom BLR over an Airtel line: ~65ms
From Taiwan (google compute instance): ~112ms
70 ms for blr digitalocean 90-110 ms for Singapore DO
120-140 ms for European DC like OVH & online.net
Thanks aws team.
I was hoping to see one more region in Chennai or Hyderabad.
http://cloudacademy.com/blog/new-aws-indian-region-cloud-aca...