Bitbucket: SLA evidence report
Bitbucket: SLA evidence report
We only started measuring Bitbucket on 2026-08-22, so the window starts there.
- Measured downtime
- 9h 13m
- Across 3 outages in this window.
- Window
- 2026-08-22 to 2026-09-06
- UTC, 15 days.
Sep 5, 2026, 7:45 PM UTC to ongoing
Single region: Australia
8h 32mmeasured in this window
Bitbucket's claim at the time: Said operational the whole time we measured this outage
Sep 5, 2026, 3:40 AM UTC to Sep 5, 2026, 4:01 AM UTC
Single region: South America
20.4mmeasured in this window
Bitbucket's claim at the time: No readable claim from their status page during this outage
Sep 3, 2026, 7:17 PM UTC to Sep 3, 2026, 7:38 PM UTC
Single region: South America
20.5mmeasured in this window
Bitbucket's claim at the time: Said operational the whole time we measured this outage
What we probed
Methodology
Every outage above is a period our probes measured Bitbucket as down from enough of the regions we check it from to count as a real outage, not a single unreliable reading (see how we tell the difference). Measured downtime is the wall-clock time inside the window an outage's regions were failing; regions failing together still count as one outage, not one per region.
Bitbucket's claim at the time comes from their own public status feed, polled on our own schedule, and is shown separately from what we measured. We never change our own reading based on what a vendor claims, and their claim never becomes our reading.
This is one external observation from RealUptime's own regions, not Bitbucket's own SLA measurement, which is usually defined against their own instrumentation and may cover a different scope than what we probe. The credit estimate above is a starting point for a conversation with Bitbucket, not a legal determination, and RealUptime is not counsel.