Isn&#x27;t the whole point of utilizing Git as a decentralized SCM so that we don&#x27;t have to rely on Bitbucket &#x2F; Github &#x2F; whoever to have 100% uptime? Sure, I get that you may be utilizing wikis, issues, or some other in-website feature, but for the most part can you not just use Git locally? I&#x27;m seeing a couple of issues here that suggest that it being down for more than an hour or two is ruining their work day, or give off the general notion that Bitbucket being down for an hour is seriously disrupting.<p>I get that maybe you need to clone a repo and you&#x27;re put off from that for the time being. But for the vast majority, you can still write code, commit code, and use all of Git&#x27;s great features without needing to be tethered to Bitbucket. Maybe only the negative posters are commenting on this, and the majority of users are going about their day despite this, but I think minor hiccups for a couple hours shouldn&#x27;t be the worst fate imaginable. I sympathize with their dev &#x2F; ops team right now, as the issue appears fairly significant (significant enough to take down SSH, HTTPS, the website, and downloads).