Minor impactResolvedDevOps

Bitbucket incident: Git operations are slow/timing out.

Bitbucket reported this minor-impact incident on its official status page on Aug 20, 2025, 07:30 UTC. It was resolved after 7h 46m.

Right now Bitbucket is operational. Live Bitbucket status →

🔔 Get alerted when Bitbucket has issuesFree · email alerts · no credit card
Aug 20, 2025, 07:30 UTC
started
Aug 20, 2025, 15:16 UTC
resolved
7h 46m
duration
Minor
impact

Affected components

  • Git via HTTPS
  • Git via SSH

Timeline

updates from Bitbucket's status page ↗
  1. resolvedAug 20, 2025, 15:16 UTC

    This incident has been resolved.

  2. monitoringAug 20, 2025, 13:24 UTC

    A root cause has been identified and a mitigation has been implemented; we're monitoring the situation.

  3. investigatingAug 20, 2025, 07:30 UTC

    - Bitbucket Cloud is investigating an incident affecting Git clone reliability. - The team is investigating the root cause and will update as soon as possible.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Bitbucket's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

How often does Bitbucket have incidents?

Bitbucket reported 3 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Bitbucket's uptime and incident history

← Previous: Bitbucket Cloud experiencing degraded performance and partial outage (Aug 19, 2025)Next: Delays in running Bitbucket Pipelines (Sep 16, 2025) →
Bitbucket incident on Aug 20, 2025: Git operations are slow/timing out. · APIStatus.watch