Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Bitbucket

    Last checked 10月28日 UTC 11:49

    Bitbucket status

    Git-based code collaboration and CI/CD tool for teams using Jira.

    Experiencing an issue?

    Bitbucket logo

    Bitbucket宕机了吗?

    Status unavailable

    Having issues with Bitbucket?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyMaintenanceCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours
    1. Status verification pending

      The latest official observation is not fresh enough to confirm current service health.

      Official provider status
      10月28日 UTC 11:49
    2. Official incident resolved

      Bitbucket Cloud - Service Disruption — **SUMMARY** On October 15, 2026, between 9:38 and 10:14 UTC, Bitbucket Cloud customers were unable to access the web interface, API, and Pipelines. Git CLI operations over HTTPS or SSH were unaffected. The incident was triggered by a deployment that did not scale quickly enough to handle peak traffic, compounded by a capacity limit in our feature flag evaluation. Automated monitoring detected the issue within 2 minutes. We restored the web interface and API by rolling back to the previous deployment and scaling it up. Pipelines performance stayed degraded until 11:54 UTC, when all services were fully recovered. **ROOT CAUSE** The trigger for this incident was a hot fix designed to mitigate a previous performance issue that was deployed using an accelerated rollout. The website auto-scaling configuration had not been tuned for a recent infrastructure change and therefore was under provisioned following the hotfix deployment. During the incident the newly deployed web and API services could not absorb traffic, and began failing. After the rollback, a surge of queued events overloaded Pipelines, delaying the processing of Pipelines jobs. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident: - **Update scaling strategy:** Update scaling thresholds and concurrency settings so website capacity is added earlier under load during hotfix deployments. - **Improve progressive rollouts:** Add smaller rollout increments and soak periods, and pre-scale new deployments for expected traffic growth. - **Improve feature flag caching mechanisms:** Adjust caching timeouts and cold-cache behavior to improve feature flag cache hits. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

      Official provider status
      10月28日 UTC 04:28

    Bitbucket outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    30 reports loaded

    Reports older than 24 hours

    New York, United States

    1 report

    Degraded performance

    10月21日 19:23 · 6天前

    +1

    United States

    4 reports

    Degraded performance

    10月21日 19:21 – 10月21日 19:23 · 6天前

    View 4 reports
    1. Report 1 · 10月21日 19:23:43

      Degraded performance

    2. Report 2 · 10月21日 19:23:21

      Degraded performance

    3. Report 3 · 10月21日 19:22:19

      Degraded performance

    4. Report 4 · 10月21日 19:21:48

      Degraded performance

    United States

    1 report

    Major outage

    10月21日 19:22 · 6天前

    United States

    1 report

    Major outage

    10月21日 19:08 · 6天前

    New York, United States

    1 report

    Degraded performance

    10月21日 19:08 · 6天前

    United States

    2 reports

    Degraded performance

    10月21日 19:06 – 10月21日 19:07 · 6天前

    View 2 reports
    1. Report 1 · 10月21日 19:07:54

      Degraded performance

    2. Report 2 · 10月21日 19:06:53

      Degraded performance

    City of Westminster, United Kingdom

    1 report

    Degraded performance

    10月21日 19:02 · 6天前

    United States

    3 reports

    Degraded performance

    10月21日 18:51 – 10月21日 18:53 · 6天前

    View 3 reports
    1. Report 1 · 10月21日 18:53:43

      Degraded performance

    2. Report 2 · 10月21日 18:52:30

      Degraded performance

    3. Report 3 · 10月21日 18:51:49

      Degraded performance

    New York, United States

    1 report

    Degraded performance

    10月21日 18:53 · 6天前

    United States

    1 report

    Major outage

    10月21日 18:53 · 6天前

    City of Westminster, United Kingdom

    1 report

    Degraded performance

    10月21日 18:47 · 6天前

    City of London, United Kingdom

    1 report

    Degraded performance

    10月21日 18:47 · 6天前

    United Kingdom

    1 report

    Degraded performance

    10月21日 18:32 · 6天前

    City of Westminster, United Kingdom

    2 reports

    Degraded performance

    10月21日 18:32 · 6天前

    View 2 reports
    1. Report 1 · 10月21日 18:32:58

      Degraded performance

    2. Report 2 · 10月21日 18:32:08

      Degraded performance

    Manchester, United Kingdom

    1 report

    Degraded performance

    10月21日 18:32 · 6天前

    City of London, United Kingdom

    1 report

    Degraded performance

    10月21日 18:32 · 6天前

    New York, United States

    1 report

    Major outage

    10月15日 9:39 · 13天前

    Chicago, United States

    1 report

    Major outage

    10月15日 9:39 · 13天前

    San Jose, United States

    1 report

    Major outage

    10月15日 9:39 · 13天前

    Loudoun County, United States

    1 report

    Major outage

    10月15日 9:39 · 13天前

    United States

    1 report

    Degraded performance

    10月15日 9:39 · 13天前

    United States

    1 report

    Major outage

    10月15日 9:39 · 13天前

    New York, United States

    1 report

    Degraded performance

    10月15日 9:39 · 13天前

    Similar reports from the same location are grouped in 5-minute windows. Counts reflect the reports shown.

    Bitbucket status history

    Official status observations, not measured service uptime.

    Bitbucket components

    Component nameStatus
    Bitbucket Website statusUp
    Bitbucket API statusUp
    Bitbucket Git via SSH statusUp
    Bitbucket Authentication and user management statusUp
    Bitbucket Git via HTTPS statusUp
    Bitbucket Webhooks statusUp
    Bitbucket Source downloads statusUp
    Bitbucket Pipelines statusUp
    Bitbucket Git LFS statusUp
    Bitbucket Email delivery statusUp

    Bitbucket incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved40m2026年10月21日UTC 17:22YesCritical
    Official status·Resolved2h 1m2026年10月15日UTC 10:07YesCritical
    Official status·Resolved4h 56m2026年10月1日UTC 02:55YesMajor
    Official status·Resolved44m2026年9月16日UTC 09:32YesMinor
    Official status·Resolved1h 28m2026年9月11日UTC 06:31YesMinor
    Official status·Resolved2h 29m2026年7月31日UTC 13:09YesUnknown
    Official status·Resolved1h 26m2026年6月11日UTC 22:48YesMinor
    Official status·Resolved1h 45m2026年5月14日UTC 05:03YesCritical

    关于 Uptimus 对 Bitbucket 的监控

    Uptimus 通过官方状态源监控 Bitbucket,并将事件、维护和组件健康状况统一为一致的服务状态。

    此页面目前包含 13 个受监控组件、56 个事件、55 个维护窗口和 10 天已知历史。

    Uptimus 是独立监控服务,与 Bitbucket 无关联。健康状态并不保证每位用户、设备或地区都未受影响。

    Uptimus 如何监控 Bitbucket

    当 Bitbucket 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。 可用历史包含 56 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Disrupted Bitbucket availability”。

    接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Bitbucket 的 13 个组件: Website, API, Git via SSH, Authentication and user management。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。

    维护通知
    当 Bitbucket 发布计划、预定或正在进行的维护时接收通知。 Uptimus 已从 Bitbucket 的可用历史中收录 55 个维护窗口。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。
    恢复通知
    当 Bitbucket 或受影响组件恢复正常运行时收到通知。 页面包含 10 天已知历史,已解决事件仍可供查看。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。
    状态消息

    在 Bitbucket 状态发生变化时接收通知

    通过电子邮件、推送和 Webhook 通知。

    开始监控

    Bitbucket 中断地图

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    查看完整地图

    Bitbucket 中断地图

    Loading report locations…

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年10月17日 UTC 16:00 · Resolved 2026年10月17日 UTC 16:30

    2. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      Note: This is the maintenance originally scheduled for October 3rd, which has now been rescheduled to October 10th. Bitbucket will be performing required maintenance on our database infrastructure for 30 minutes on Saturday, October 10th, 2026 at 16:00 UTC. The maintenance will require a short period of downtime at the beginning of the maintenance window, affecting all Bitbucket Cloud services including the Bitbucket website, Git operations via SSH and HTTPS, API requests, and Bitbucket Pipelines. Performance degradation is possible throughout the window. We encourage all of our users to plan their operations around this window.

      Started 2026年10月10日 UTC 16:00 · Resolved 2026年10月10日 UTC 16:30

    3. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      Bitbucket will be performing required maintenance on our database infrastructure for 30 minutes on Saturday October 3rd 2026 at 16:00 UTC. The maintenance will require a short period of downtime at the beginning of the maintenance window, affecting all Bitbucket Cloud services including the Bitbucket website, Git operations via SSH and HTTPS, API requests, and Bitbucket Pipelines, and performance degradation is possible throughout the window. We encourage all of our users to plan their operations around this window.

      Started 2026年10月3日 UTC 16:00 · Resolved 2026年10月3日 UTC 16:30

    4. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      We will be undergoing scheduled maintenance during this time.

      Started 2026年10月3日 UTC 16:00 · Resolved 2026年10月3日 UTC 16:30

    5. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年8月30日 UTC 00:00 · Resolved 2026年8月30日 UTC 02:00

    6. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年6月13日 UTC 17:00 · Resolved 2026年6月13日 UTC 19:00

    7. ✓

      Bitbucket Connect app maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年4月10日 UTC 00:30 · Resolved 2026年4月10日 UTC 01:30

    8. ✓

      Bitbucket Cloud - Database Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年2月21日 UTC 16:00 · Resolved 2026年2月21日 UTC 22:00

    Uptimus 保存 Bitbucket 发布的事件标题,并与标准化状态一起显示。 可用历史包含 56 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Disrupted Bitbucket availability”。
    状态详情
    事件和维护更新会被保留,以便跟踪调查、缓解和恢复过程。 Uptimus 保存的近期官方更新为:“On October 21, 2026, Bitbucket experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.”。
    组件状态筛选
    选择所有组件或仅选择使用的 Bitbucket 产品。官方通知会遵循该选择。 Uptimus 当前跟踪 Bitbucket 的 13 个组件: Website, API, Git via SSH, Authentication and user management。 筛选只改变官方提醒的发送范围,不会从公开历史中移除事件。

    常见问题

    在 Bitbucket 状态发生变化时接收通知

    开始监控
    Similar services
    Comparison

    Bitbucket:Uptimus 与 Downdetector 对比

    Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。

    Bitbucket:Uptimus 与 Downdetector 对比
    比较标准UptimusDowndetector
    Bitbucket 的社区中断报告已包含已包含
    区分个别报告和大范围中断的自适应基线已包含已包含
    24 小时报表活动和区域中断视图已包含已包含
    在一个工作区管理网站、状态提供商、Steam 游戏及 Android 应用和游戏已包含独立产品
    从同一工作区发送邮件、推送和 Webhook 告警已包含独立产品
    Bitbucket 的官方事件更新和状态时间线已包含以用户报告为主
    分别展示组件健康与维护窗口已包含公共页面功能有限
    已包含以用户报告为主 · 公共页面功能有限独立产品

    The current official status of Bitbucket cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Bitbucket in the last 24 hours. Last official check: 10月28日 UTC 11:49.

    社交信号

    1 post from X and Reddit.

    01
    Reddit
    r/isdownapp·27天前
    Posted by u/isdownapp

    Bitbucket is having a major incident

    Job processing and scheduling is degraded affecting multiple Atlassian products. Are you having issues with Bitbucket? If yes, please share details in the comments.

    评价此服务

    您如何评价过去一个月的 Bitbucket?

    暂无评价

    (每月限制一条评价)

    更多监控服务

    发现其他流行服务及其当前状态

    浏览所有服务
    SignalPhasmophobiaKayrrosGearhostAblyOverleafEcobeeLandingiEsa

    社区讨论

    分享您对 Bitbucket 的看法

    A
    @Juan Manuel Samudio·Guest
    anyone see this error? upstream connect error or disconnect/reset before headers. reset reason: connection timeout
    7 days ago
    @Jabar Shahid·Guest
    bitbucket is not working to me, anyone?
    13 days ago
    @Jabar Shahid·Guest
    bitbucket is not working to me, anyone? facing this error: "upstream connect error or disconnect/reset before headers. reset reason: connection timeout"
    13 days ago
    @Andre Cerqueira Crespo·Guest
    bitbucket API is not working to me, anyone? Jenkins can't return job status to bitbucket.
    2 months ago
    @Vitor Jr·Guest
    Down since 8:00AM BRT
    3 months ago
    @Andres·Guest
    Bitbucket is stopping me from pushing changes, it returns 500 error
    3 months ago
    @rava·Guest
    pipeline not working today
    3 months ago
    @FD·Guest
    SSH keys are broken for auth
    5 months ago