HI Guys, I'm also facing this kind of issue. There's anyone here know the solution. Even I used the SSH, it doesn't work anyway.

I confirm, now issue is solved. Thank you

After I sent an email to support@bitbucket.org, and a colleague contacted BitBucket billing, things appear resolved for the moment. I have been notified that "Degraded service" got "restored", no reason given. Tested from 2 clients (Win7 vs. Win10, both TortoiseHg 4.7), works as of ~6pm PDT Sunday. Good job!

Just to keep everyone in the loop who is coming here from Google, it looks like as of 15 minutes ago Atlassian is aware of the issue and working on it. I just received this update on my support request:

Ronald Chia commented:

Hi there,

Thank you for getting in touch with Bitbucket Support Team.
Our engineering team has been notified and is currently investigating the issue causing this error.

Based on our current investigation, the issue happens while pushing using Mercurial via https protocol.
Hence, as a workaround, we would suggest using SSH protocol while our team working on it.
[Set up an SSH key - Atlassian Documentation

We apologize for any inconvenience, we will give you an update when we know more on the issue.
In addition to it, we've updated our status page and we would suggest subscribing to the incident reports for more updates in regards to it as well:
https://status.bitbucket.org/incidents/8xphd675jq6x

Please, feel free to let us know if you have any other questions.

Thank you.
Bitbucket Cloud Support team.

Same for me. 502. Bad Gateway.

Service has been down for at least 18 hours.

Identical problem; ours is a professional operation, we are paying for the service, and it is down and ironiously marked RESOLVED. First failure registered Saturday 9/22 ~10pm PDT. Not been able to push since, pull keeps working.

Fix ASAP, please. If not resolved by Monday morning, my first action (as I can't code) will be to bring it up with our COO and get budgeted to start looking at alternatives.

I have the exact same problem, mercurial repo, using TortoiseHg.

Hi, absolutely same issue. I was able to push to my repository all the time until now (23 Sep, 2018). Please, fix asap!
Windows 10, Tortoise 4.3.1

Can confirm this, neither command line tool hg nor TortoiseHg worked. Just experienced this since today. Yesterday everything was working fine!

@Блажо Ђуровић - Yes, I'm using the command line hg tool on Ubuntu Linux, and I see the 502 error as well. I sent a support ticket to support@bitbucket.org hours ago but haven't heard back.