Bitbucket: Disrupted Bitbucket availability
Affected components: Source downloadsPurchasing & LicensingGit via HTTPSPackagesGit LFSWebsiteAPIAuthentication and user managementGit via SSHWebhooksPipelinesSignupEmail delivery
Discussed on Hacker News
- 1 points · 2 comments · posted · posted 18 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Timeline of updates
- investigating
We are actively investigating reports of a service disruption affecting Bitbucket. We will share updates here as more information is available.
- investigating
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing some recovery, and will continue to share additional updates here as more information is available.
- monitoring
The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.
- resolved
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.
Changes Rewindex caught on this incident
- Critical incident: Disrupted Bitbucket availability
- Incident updated: Disrupted Bitbucket availability
- Incident updated: Disrupted Bitbucket availability
- Incident updated: Disrupted Bitbucket availability
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).