Bitbucket out of order

Unfortunately Bitbucket seems to be down, but the status page reports all systems operational.

And Atlassian seems to have no place to report the issue either.

(._.) ~ ︵ ┻━┻(._.) ~ ︵ ┻━┻

3 answers

1 vote

Confirmed. I despise that all-too-common bad design pattern:

Entire site is down

Something went wrong

Bitbucket is experiencing a problem that is preventing this request from being successful. Rest assured that we are aware and are working to fix it as quickly as possible. For more information please refer to https://status.bitbucket.org/. Alternatively, you're welcome to raise an issue with our support team at https://support.atlassian.com/contact.

status page cheerfully reports that everything is up and great! 100% uptime! No issues!
"you're welcome to raise an issue with our support team": No, you're not. At least if you're not on a paid plan.

Look: if people are visiting your status page, the status page itself should probe the site and make sure there are no current or ongoing problems. This is easy to do. It's an internal app. It can send a query and look for the proper response. It can check logs. It can confirm that the main page works at all. And then it can report the problem and show the status honestly instead of lying and telling everyone that everything's just peachy. Sorry, but that "100% uptime" is already dinged, even if the outage is just a few minutes.

And "Report a problem" should actually do something, not just refer people to the community where they can gripe about it to each other. If nothing else, "145 people have noted problems in the last hour. We're looking into it."

This is why third-party status monitors like DownDetector are far more trustworthy than a site policing itself.

If "we are aware and are working to fix it as quickly as possible", why is your own status page not aware, by the way?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

P.S. Another design gripe. If you already have logic in a server that's able to tell the user that "Something went wrong", then the server already knows that something went wrong. You should not be asking your customers to report the issue you know about for you.

It should be more like:

"The BitBucket service is returning an (invalid response / error / timeout....). This issue has automatically been reported to our support team. This was first reported at (date/time). You can track our progress and resolution on it here."

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I came to the same conclusion earlier on.
Atlassian does not seem to bother changing it.

If Bitbucket is down, we just have to hope someone inside Atlassian discovers that by themselves sometime.

The status tool obviously doesn't seem to monitor if things are up or not....

٩(̾●̮̮̃̾•̃̾)۶

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This is also kind of interesting:

$ gp -f
Enumerating objects: 77, done.
Counting objects: 100% (77/77), done.
Delta compression using up to 10 threads
Compressing objects: 100% (53/53), done.
Writing objects: 100% (53/53), 37.87 KiB | 4.73 MiB/s, done.
Total 53 (delta 31), reused 0 (delta 0), pack-reused 0 (from 0)
remote: <!DOCTYPE html>
remote: <html lang="en">
remote: <head>
remote: <meta charset="utf-8">
remote: <title>500 &mdash; Something went wrong &mdash; Bitbucket</title>