February 8, 1:51 pm EST: Our Development team has continued to monitor and research this issue, to prevent it from happening again, and found that the issue originated at our Microsoft Azure data center:
Starting as early as 13:00 UTC on 08 Feb 2017, a subset of customers using SQL Database in North Central US may experience intermittent issues or failure notifications while attempting to connect databases in this region to web app resources. Engineers are aware of this issue and are actively investigating.
You can follow status updates here.
February 8, 10:03 am EST: OnBoard is fully restored. Here is a summary of the issue:
On 2/8/17, We noticed some SQL request limits causing delays in response timing, and altered our resource allocations to accommodate for the performance problems. While the re-allocation was occurring, the internal firewall started refusing connections to our background role that monitors/manages data source availability. As a result, data was not accessible from some of our SQL databases. We have corrected the firewall lockout, and restored connection status to all SQL databases.
February 8, 8:53 am EST: At this time, we are experiencing a service interruption of OnBoard. We are working diligently to resolve this issue, and appreciate your patience.
Please follow this article for updates on this issue.