← Live dashboard

Degraded performance of Bitbucket

ResolvedminorOfficial source confirmedMulti-region impactFirst recorded update Jun 11, 2026, 10:48 PM · Resolved Jun 12, 2026, 12:14 AM

On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

Bitbucket live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Bitbucket now? Check the current status

Affected services

Git LFSEmail deliveryPackagesWebhooksAuthentication and user managementGit via SSHWebsiteGit via HTTPSPurchasing & LicensingAPISource downloadsPipelinesSignup

Updates (4)

  1. Jun 12, 2026, 12:14 AM
    Degraded performance of Bitbucket

    On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

    Bitbucket ↗
  2. Jun 11, 2026, 11:58 PM
    Degraded performance of Bitbucket

    The performance degradation of Bitbucket has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

    Bitbucket ↗
  3. Jun 11, 2026, 11:21 PM
    Degraded performance of Bitbucket

    We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.

    Bitbucket ↗
  4. Jun 11, 2026, 10:48 PM
    Degraded performance of Bitbucket

    We are actively investigating reports of performance degradation affecting Bitbucket OAuth login. We will share updates here as more information is available.

    Bitbucket ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Bitbucket's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.