Space for ads
Checked every 5 minutes · How we measure this
As of 15:10 EDT on 8 Sep 2026, bitbucket.org responded to our check in 207 ms, with 95.65% availability over the last 24 hours.
Checked every 5 minutes · last checked 9 minutes ago
The line is response time measured from our probe to bitbucket.org, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by Bitbucket on its own status page. Verify on their status page.
Access to bitbucket.org
Access to api.bitbucket.org
Access to Git over SSH.
Access to Git repositories via HTTPS
The Bitbucket webhooks service
Archive (zip, tar.gz, bzip) downloads of repositories
Continuous integration and delivery for Bitbucket repos
Git Large File Storage
0 problem reports
No incidents recorded since monitoring began. Monitoring for Bitbucket records every incident lasting ten minutes or more.
Bitbucket is responding normally. Our last automated check of bitbucket.org completed 9 minutes ago and succeeded in 207 ms. Over the past 24 hours the service answered 95.65% of our checks.
Measured from our automated checks, Bitbucket has been available 95.65% over 24 hours, 95.65% over 7 days, 95.65% over 30 days. We have recorded no incidents in the last 30 days.
Bitbucket has averaged 1,158 ms across our successful checks in the past 24 hours, which is slower than ideal and may feel sluggish on a weak connection. Response time is measured from our probe to bitbucket.org and does not include rendering time in your browser.
Our probe is reaching bitbucket.org normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://bitbucket.org/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than Bitbucket. On Windows run ping bitbucket.org and nslookup bitbucket.org in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load bitbucket.org in a private or incognito window. If it works there, clear cookies and site data for bitbucket.org in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
