<a href="https:&#x2F;&#x2F;twitter.com&#x2F;gitlabstatus" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;gitlabstatus</a> on <a href="https:&#x2F;&#x2F;status.gitlab.com" rel="nofollow">https:&#x2F;&#x2F;status.gitlab.com</a> mentions <i>Azure</i> cloud several times.<p><pre><code>  &quot;The rsync to *Azure* SSD got interrupted last night 
  when we had an outage. Restarting it now.&quot; - 18th Dec

  &quot;This means service will partially restore over the next
  few minutes and then go away again once the *Azure* 
  restart command succeeds.&quot; 

  &quot;Looks like we are headed for the ‘double restart’ 
  scenario. The NFS server came back on its own but 
  *Azure* is still busy restarting it.&quot;

  &quot;*Azure* restart of the NFS server is in progress&quot;

  &quot;Depending on whether the machine is stuck or already 
  rebooting. No way to tell with *Azure*.&quot;

  &quot;*Azure* CLI restart of the NFS server finished, that is 
  usually a good sign.&quot;

  &quot;We are experimenting with copying data out of our 
  current *Azure* storage account. Unfortunately the 
  copying affects http:&#x2F;&#x2F;gitlab.com&quot; - 1st Dez

  &quot;Azure incident quote: Network Infrastructure and 
  Storage - East US 2 - Partial Service Interruption 
  [East US 2]&quot; - 11. Nov

  &quot;Seems to be a major @azure outage...&quot; - 11th Nov

  &quot;At 18:00UTC we will start migrating PostgreSQL to Azure 
  Premium Storage gitlab.com&#x2F;gitlab-com&#x2F;ope… , expect 15 
  minutes downtime.&quot; - 10. Nov

  &quot;trying another Azure restart of the NFS server &quot; - 6th Nov

  &quot;In the last 24h, we had two reboots of our Redis server 
  seemingly caused by Azure (no kernel panics) and VHD 
  read errors on the NFS server&quot; - 5th Nov

  &quot;Azure are sponsoring us so we are saving a lot on our 
  hosting bill. We are documenting the move on an upcoming 
  blog post.&quot; - 16th Oct
</code></pre>
There have appearently been really big troubles, starting in November! Is Azure cloud that bad or is it a problem on your side? What about moving to AWS&#x2F;Google&#x2F;Rackspace?