Vendor Status Watch

← all vendors

Bitbucket status history

Current state: operational — “All Systems Operational” per https://bitbucket.status.atlassian.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

2incidents, last 30 days
3incidents, last 90 days
18incidents on record
Incidents per week, last 12 weeks:

How long do Bitbucket incidents last?

2.5 hmedian incident duration18 measured
18.2 h90th percentile1 in 10 ran longer
2.5 hmedian, major/critical only5 incidents

From 18 incidents with a vendor-posted start and resolve time. Longest on record: Core-daily Pipeline is delayed for 25th Aug run — 24.3 h (2025-08-26 15:06 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (18)

StartedIncidentStatusImpactDuration
2026-09-16 09:32 UTCDelays with Bitbucket Pipelines Executionresolvedminor43 min
2026-09-11 06:31 UTCIntermittent reliability issue with Bitbucket Cloudresolvedminor1 h 28 min
2026-07-31 13:09 UTCBitBucket Site fails to Loadresolvednone2 h 28 min
2026-06-11 22:48 UTCDegraded performance of Bitbucketresolvedminor1 h 26 min
2026-05-14 05:03 UTCUsers experiencing issues accessing multiple Atlassian productspostmortemcritical1 h 44 min
2026-05-08 01:31 UTCMultiple Atlassian services are experiencing issuespostmortemminor18 h 13 min
2026-04-16 20:23 UTCBitbucket Pipelines degraded performanceresolvedminor21 min
2026-04-13 07:29 UTCUsers experiencing issues with login across Atlassian productspostmortemminor2 h 47 min
2026-03-12 08:48 UTCDegraded performance of Bitbucket cloudresolvedminor3 h 45 min
2026-03-06 02:44 UTCDisrupted Bitbucket availabilitypostmortemcritical2 h 27 min
2026-01-28 16:49 UTCDisrupted Bitbucket availability in eu-west-1resolvedminor3 h 11 min
2026-01-07 16:23 UTCUnable to reach bitbucket sitepostmortemcritical2 h 29 min
2026-01-07 06:05 UTCBitbucket workspace invitations failing for all usersresolvedminor35 min
2025-12-27 04:42 UTCOutbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Productspostmortemcritical37 min
2025-11-11 16:59 UTCBitbucket availability degradedpostmortemcritical4 h 11 min
2025-10-20 07:56 UTCAtlassian Cloud Services impactedpostmortemnone21 h 28 min
2025-09-16 04:00 UTCDelays in running Bitbucket Pipelinesresolvedminor30 min
2025-08-26 15:06 UTCCore-daily Pipeline is delayed for 25th Aug runresolvednone24 h 19 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Bitbucket with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "bitbucket"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}