Where does this status come from?

From Bitbucket's own status page API at https://bitbucket.status.atlassian.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Bitbucket's words.

How can my agent or app check Bitbucket status?

Fetch https://upbutler.com/status/bitbucket/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"bitbucket"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Bitbucket's?

Add "bitbucket" to the dependencies of your UpButler workspace. When one of your monitors fails while Bitbucket has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Bitbucket down?

Right now

No. Bitbucket is operational.

No incidents reported.

Read from bitbucket.status.atlassian.com 3 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/bitbucket/status.agent.json

MCP: upstream_status {"service":"bitbucket"}

Git hosting and Pipelines.

What Bitbucket reports

Operational

Taken as is from Bitbucket's own status page API. Incident titles and component names below are theirs.

Open bitbucket.status.atlassian.com

UpButler's independent probe

There is no keyless endpoint of Bitbucket that says anything useful, so UpButler does not probe it. To check your own Bitbucket account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Bitbucket components

13 operational

WebsiteOperational
APIOperational
Git via SSHOperational
Authentication and user managementOperational
Git via HTTPSOperational
WebhooksOperational
Source downloadsOperational
PipelinesOperational
Git LFSOperational
Email deliveryOperational
Purchasing & LicensingOperational
SignupOperational
PackagesOperational

Bitbucket incidents, last 90 days

1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Bitbucket.

Started (UTC)	Incident	Impact	Lasted
2026-10-01 02:55	Job processing and scheduling is degraded affecting multiple Atlassian products	major	4 h 56 min

Tell your outage from Bitbucket's

Declare that your project depends on Bitbucket. When one of your monitors fails while Bitbucket has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - bitbucket

Ask before you retry

curl -s https://upbutler.com/status/bitbucket/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "bitbucket",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Bitbucket down right now?: No. As of 2026-10-10 05:10 UTC, Bitbucket is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Bitbucket's own status page API at https://bitbucket.status.atlassian.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Bitbucket's words.
How can my agent or app check Bitbucket status?: Fetch https://upbutler.com/status/bitbucket/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"bitbucket"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Bitbucket's?: Add "bitbucket" to the dependencies of your UpButler workspace. When one of your monitors fails while Bitbucket has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Bitbucket. Status and incident text belong to Bitbucket and are read from their public status source; the probe result is UpButler's own measurement.