Skip to content

Outage tracker / Bitbucket

Is Bitbucket down?

I'm having a problem

Vendor reports no incidentWhat Bitbucket reports

Bitbucket reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:21 UTC.

Bitbucket's status page

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 1 minute ago

Our checks of Bitbucket pass from all 10 regions we check.

As of Nov 5, 2026, 3:26 PM UTC, RealUptime's checks of Bitbucket passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:26 PM UTC
US-East962 msChecks passing
US-West869 msChecks passing
Europe760 msChecks passing
Asia-Pacific1413 msChecks passing
US-Central732 msChecks passing
Canada467 msChecks passing
UK521 msChecks passing
Southeast Asia863 msChecks passing
Australia546 msChecks passing
South America1464 msChecks passing
their status pagetheir claim, not our reading

Bitbucket reports: All systems operational (“All Systems Operational”)

from Bitbucket's own status page, checked Nov 5, 2026, 2:27 PM UTC
Bitbucket's own status page shows no incident, and our checks of Bitbucket pass right now.

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

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 763ms2026-10-08 UTC: p95 888ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 792ms2026-10-11 UTC: p95 658ms2026-10-12 UTC: p95 706ms2026-10-13 UTC: p95 712ms2026-10-14 UTC: p95 725ms2026-10-15 UTC: p95 723ms2026-10-16 UTC: p95 819ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 733ms2026-10-23 UTC: p95 854ms2026-10-24 UTC: p95 653ms2026-10-25 UTC: p95 683ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 769ms2026-10-08 UTC: p95 748ms2026-10-09 UTC: p95 727ms2026-10-10 UTC: p95 803ms2026-10-11 UTC: p95 751ms2026-10-12 UTC: p95 733ms2026-10-13 UTC: p95 767ms2026-10-14 UTC: p95 913ms2026-10-15 UTC: p95 836ms2026-10-16 UTC: p95 866ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 986ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.6sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 817ms2026-10-08 UTC: p95 778ms2026-10-09 UTC: p95 743ms2026-10-10 UTC: p95 740ms2026-10-11 UTC: p95 548ms2026-10-12 UTC: p95 599ms2026-10-13 UTC: p95 586ms2026-10-14 UTC: p95 632ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 770ms2026-10-17 UTC: p95 769ms2026-10-18 UTC: p95 824ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 795ms2026-10-22 UTC: p95 900ms2026-10-23 UTC: p95 812ms2026-10-24 UTC: p95 808ms2026-10-25 UTC: p95 709ms2026-10-26 UTC: p95 731ms2026-10-27 UTC: p95 754ms2026-10-28 UTC: p95 982ms2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 963ms2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 985ms2026-11-02 UTC: p95 872ms2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 929ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-Central
1.5sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 851ms2026-10-08 UTC: p95 858ms2026-10-09 UTC: p95 935ms2026-10-10 UTC: p95 814ms2026-10-11 UTC: p95 670ms2026-10-12 UTC: p95 848ms2026-10-13 UTC: p95 977ms2026-10-14 UTC: p95 920ms2026-10-15 UTC: p95 794ms2026-10-16 UTC: p95 674ms2026-10-17 UTC: p95 618ms2026-10-18 UTC: p95 824ms2026-10-19 UTC: p95 756ms2026-10-20 UTC: p95 779ms2026-10-21 UTC: p95 899ms2026-10-22 UTC: p95 909ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Canada
1.5sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 937ms2026-10-08 UTC: p95 976ms2026-10-09 UTC: p95 960ms2026-10-10 UTC: p95 692ms2026-10-11 UTC: p95 825ms2026-10-12 UTC: p95 722ms2026-10-13 UTC: p95 688ms2026-10-14 UTC: p95 726ms2026-10-15 UTC: p95 943ms2026-10-16 UTC: p95 598ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 813ms2026-10-23 UTC: p95 819ms2026-10-24 UTC: p95 782ms2026-10-25 UTC: p95 907ms2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
UK
1.2sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 774ms2026-10-08 UTC: p95 543ms2026-10-09 UTC: p95 570ms2026-10-10 UTC: p95 498ms2026-10-11 UTC: p95 489ms2026-10-12 UTC: p95 573ms2026-10-13 UTC: p95 767ms2026-10-14 UTC: p95 657ms2026-10-15 UTC: p95 558ms2026-10-16 UTC: p95 578ms2026-10-17 UTC: p95 828ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 971ms2026-10-23 UTC: p95 794ms2026-10-24 UTC: p95 815ms2026-10-25 UTC: p95 663ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 616ms2026-10-28 UTC: p95 737ms2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 761ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Southeast Asia
2.0sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 916ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.8s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 989ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Australia
1.9sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 914ms2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
South America
2.8sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.6s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 748ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 2.4s2026-10-23 UTC: p95 8.6s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5

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.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Bitbucket's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 962msstatus code: 200checked: Nov 5, 2026, 3:24 PM UTC
      0 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-West
      Checks passinglatency: 869msstatus code: 200checked: Nov 5, 2026, 3:24 PM UTC
      0 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-Central
      Checks passinglatency: 732msstatus code: 200checked: Nov 5, 2026, 3:11 PM UTC
      0 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.
    • Canada
      Checks passinglatency: 467msstatus code: 200checked: Nov 5, 2026, 3:26 PM UTC
      0 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 America
    Checks passinglatency: 1464msstatus code: 200checked: Nov 5, 2026, 3:18 PM UTC
    0 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.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 760msstatus code: 200checked: Nov 5, 2026, 3:13 PM UTC
      0 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.
    • UK
      Checks passinglatency: 521msstatus code: 200checked: Nov 5, 2026, 3:17 PM UTC
      0 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 Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1413msstatus code: 200checked: Nov 5, 2026, 3:11 PM UTC
      0 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 Asia
      Checks passinglatency: 863msstatus code: 200checked: Nov 5, 2026, 3:12 PM UTC
      0 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.
    • Australia
      Checks passinglatency: 546msstatus code: 200checked: Nov 5, 2026, 3:25 PM UTC
      0 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

Disrupted Bitbucket availability, 40mdeclared on their status page2026-10-21
Bitbucket Cloud - Service Disruption, 2h 1mdeclared on their status page2026-10-15
Job processing and scheduling is degraded affecting multiple Atlassian products, 4h 56mdeclared on their status page2026-10-01
Delays with Bitbucket Pipelines Execution, 44mdeclared on their status page2026-09-16
Intermittent reliability issue with Bitbucket Cloud, 1h 28mdeclared on their status page2026-09-11
BitBucket Site fails to Load, 2h 29mdeclared on their status page2026-07-31
Degraded performance of Bitbucket, 1h 26mdeclared on their status page2026-06-11
Users experiencing issues accessing multiple Atlassian products, 1h 45mdeclared on their status page2026-05-14

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 servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Bitbucket uptime by RealUptime's checksLive, from this page's own readings.
[![Bitbucket uptime by RealUptime's checks](https://realuptime.io/outages/bitbucket/badge.svg?days=30)](https://realuptime.io/outages/bitbucket)
<a href="https://realuptime.io/outages/bitbucket"><img src="https://realuptime.io/outages/bitbucket/badge.svg?days=30" alt="Bitbucket uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

What we check

primaryfunctional: live API
https://api.bitbucket.org/2.0/repositories/atlassian
secondary
https://bitbucket.org/
secondary
https://bitbucket.status.atlassian.com/api/v2/status.json

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

RealUptime is not affiliated with Bitbucket; the name identifies what we checked, and nothing here speaks for Bitbucket's own team. We send a single web request to Bitbucket from 10 regions on our own schedule and time the response. We do not see inside Bitbucket's systems, do not use an account or real transaction, and are not the same signal Bitbucket's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Bitbucket is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.