Bitbucket twitter account claims it was a result of routine file maintenance and it has been resolved, but they will continue to monitor: https://twitter.com/bitbucket