<a href="https://twitter.com/BitbucketStatus/status/788024762014412804" rel="nofollow">https://twitter.com/BitbucketStatus/status/78802476201441280...</a> They've posted on their Twitter account with essentially the same content as well.<p>It's been down for almost 40 minutes for us, completely blocking a scheduled release. Didn'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's git over SSH that's having a problem. You can switch a repo like this:
<a href="https://help.github.com/articles/changing-a-remote-s-url/" rel="nofollow">https://help.github.com/articles/changing-a-remote-s-url/</a>
As someone who is effected by this:<p>Are there any good ways to push/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.