Changes / Bitbucket / Some Bitbucket customers unable to push and clone
Bitbucket: Major incident: Some Bitbucket customers unable to push and clone
Summary
Bitbucket reported a major-impact degradation affecting push and clone operations over Git via HTTPS and Git via SSH for some customers. The incident started at 2025-08-01 08:16 UTC and was resolved at 2025-08-01 09:22 UTC, lasting 1 h 5 min; the vendor confirmed normal service had resumed.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 73%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Some Bitbucket customers unable to push and clone
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-08-01 08:16 UTC
Before: not present
After: 2025-08-01 09:22 UTC
Before: not present
After: Git via HTTPS, Git via SSH
Before: not present
After: We are investigating reports of intermittent errors for some Atlassian Bitbucket Cloud customers. We will provide more details once we identify the root cause.
Before: not present
After: Between 08:00UTC to 09:00UTC, we experienced degraded performance with push and clone operations for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some Bitbucket customers unable to push and clone (this change) Bitbucket reported a major-impact degradation affecting push and clone operations over Git via HTTPS and Git via SSH for some customers. The incident started at 2025-08-01 08:16 UTC and was resolved at 2025-08-01 09:22 UTC, lasting 1 h 5 min; the vendor confirmed normal service had resumed. | Major incident |
All Bitbucket changes → · Bitbucket profile · Markdown · JSON