Is Bitbucket down?
Vendor reports no incidentWhat Bitbucket reports
Bitbucket reports no incident on its status page.
As of the last successful poll, 2026-10-22 21:50 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 5 minutes ago
Our checks of Bitbucket pass from all 10 regions we check.
As of Oct 22, 2026, 9:47 PM UTC, RealUptime's checks of Bitbucket passed in all 10 regions that returned a reading.
Bitbucket reports: All systems operational (“All Systems Operational”)
Bitbucket's own component breakdown, as they publish it
- WebsiteOperational
- APIOperational
- Git via SSHOperational
- Authentication and user managementOperational
- Git via HTTPSOperational
- WebhooksOperational
- Source downloadsOperational
- PipelinesOperational
- Git LFSOperational
- Email deliveryOperational
- Purchasing & LicensingOperational
- SignupOperational
- PackagesOperational
These are Bitbucket's components, named and scored by Bitbucket. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Bitbucket's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Bitbucket response time, by region
Check your own site while you wait on Bitbucket
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Bitbucket. It cannot diagnose Bitbucket's own systems.
What we measured, function by function
Bitbucket answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Bitbucket reports an incident on its status page, and again when it reports it resolved.
Get an email when Bitbucket reports an incident
Email me when Bitbucket reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 448msstatus code: 200checked: Oct 22, 2026, 9:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Bitbucket normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 925msstatus code: 200checked: Oct 22, 2026, 9:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Bitbucket normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 422msstatus code: 200checked: Oct 22, 2026, 9:38 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Bitbucket normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 502msstatus code: 200checked: Oct 22, 2026, 9:37 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Bitbucket normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 2519msstatus code: 200checked: Oct 22, 2026, 9:39 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Bitbucket normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 546msstatus code: 200checked: Oct 22, 2026, 9:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Bitbucket normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 452msstatus code: 200checked: Oct 22, 2026, 9:37 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Bitbucket normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1322msstatus code: 200checked: Oct 22, 2026, 9:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Bitbucket normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 816msstatus code: 200checked: Oct 22, 2026, 9:37 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Bitbucket normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1037msstatus code: 200checked: Oct 22, 2026, 9:38 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Bitbucket normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Bitbucket, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Bitbucket yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Bitbucket since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Bitbucket covering any window you pick, with our check readings and Bitbucket's own claim at the time, side by side.
Full check history for Bitbucket: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
To cite this page: RealUptime, "Is Bitbucket down?", https://realuptime.io/outages/bitbucket. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: api.bitbucket.org