Bitbucket experiencing major outage for repositories connecting via SSH

<a href="https:&#x2F;&#x2F;twitter.com&#x2F;BitbucketStatus&#x2F;status&#x2F;788024762014412804" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;BitbucketStatus&#x2F;status&#x2F;78802476201441280...</a> They&#x27;ve posted on their Twitter account with essentially the same content as well.<p>It&#x27;s been down for almost 40 minutes for us, completely blocking a scheduled release. Didn&#x27;t realise until now how much of a dependency Bitbucket was to us - definitely lessons to be learned here.

Note - HTTPS git methods still work; it&#x27;s git over SSH that&#x27;s having a problem. You can switch a repo like this: <a href="https:&#x2F;&#x2F;help.github.com&#x2F;articles&#x2F;changing-a-remote-s-url&#x2F;" rel="nofollow">https:&#x2F;&#x2F;help.github.com&#x2F;articles&#x2F;changing-a-remote-s-url&#x2F;</a>

As someone who is effected by this:<p>Are there any good ways to push&#x2F;pull from multiple upstreams for whole teams? That also works with your whole CI workflow?<p>So that you for example can have copies of the repository available on both Bitbucket, GitHub, and GitLab at the same time.