Is Bitbucket down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, bitbucket.org is responding normally to HostTracker's monitoring network, and has been up for 21d 2h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, bitbucket.org is responding normally to HostTracker's monitoring network, and has been up for 21d 2h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

It might be, and it's worth checking. Bitbucket and Jira both authenticate through the same shared Atlassian identity system, so a login incident there blocks access to both products at once even though each one's own underlying service - repositories in Bitbucket's case - keeps running fine behind that gate. If Bitbucket won't let you sign in, checking /en/is-jira-down for the same symptom is a fast way to confirm whether the problem is the shared identity layer rather than Bitbucket specifically.

Often not a full outage. Pipelines has its own processing capacity separate from Git hosting, and heavy demand across many repositories at busy times can queue CI runs for longer than usual without anything actually being broken. If code can still push and pull normally over Git while only Pipelines runs are delayed, that points at CI capacity rather than a platform-wide incident.

Webhook delivery runs through its own processing path, and a backlog there can delay a notification reaching an integration without the rest of Bitbucket being affected at all. Repository operations, browsing, and Pipelines can all be running normally while a webhook queue lags behind, which is a narrower and usually short-lived issue rather than a sign of a wider incident.