New Databases are failing in East Asia And Japan

Question

Creating new SQL database & server at present fail in East Asia & Japan locations -> After creating can't connect - VS 2013 also prompts for firewall despite Azure Management panel showing FW rules in place.
SQL Returns Error 64. (For the above locations)
Creating new SQL DB's & servers in US locations appears fine.
I often feel the guys that are supposed to manage azure are asleep at the wheel when it comes to non-US locations. It shouldn't have to be me that tells you when your services aren't provisioning correctly. IF anyone could be bothered please reply when the
services are functioning again in East Asia... *It's also silly I need to pay Azure to submit a ticket to tell them they're stuff is broken, Azure has once again wasted my time. If someone there wants to post links to obscure webpages that (of course) don't
fix the problem don't bother.
Minor Rant over ... just get things fixed.

Answer 1

Hi XinTW,
Thanks for posting here.
There was an outage reported on Last Friday with VS online and has been resolved on the same day.
I suggest you to follow these steps and let us know if the issue still persists.
Troubleshooting Connection-loss Errors
Check the status of the SQL Database service: To check the status of the SQL Database service, use the
Azure Health Status .
The status page contains current service status information and historical service data.
Trace connections: When the client application
connects to SQL Database, CONTEXT_INFO (Transact-SQL) is set with a unique session specific GUID value automatically. You may retrieve this GUID value and use it in your application to trace the connectivity problems when necessary. For example code, see
Development Considerations in SQL Database   
Check DMV: SQL Database enables a subset of DMVs
to diagnose the performance problems, which might be caused by blocked or long-running queries, resource bottlenecks, poor query plans, and so on. For a list of supported and unsupported DMVs in SQL Database.
The
Monitoring Windows Azure SQL Database Using Dynamic Management Views 
topic also provides examples on how to detect common performance problems by using the DMV in SQL Database.
Stress test: To reduce connection-losses from excessive
resource usage, you can stress test your database application by slowly increasing the test workload until the desired level of concurrency is reached. When stress testing triggers a connection-loss, identify the resource limits by analyzing the returned reason
codes and tune your application appropriately. For more information on reason codes, see
Reason Codes 
in the SQL Database Database documentation.
Hope this helps you.
Girish
Prajwal