Bitbucket logo

Bitbucket outage on 21 October 2026

Critical
Resolved · 17:22–18:03 UTC
Get alerts for Bitbucket

An email when it goes down, and when it’s back.

“Disrupted Bitbucket availability”

Bitbucket had a critical outage on 21 October, when the status page reported that its website, Git over HTTPS and SSH, API, Pipelines, authentication and all other listed components were disrupted from 17:22 to 17:51 UTC. The incident stayed open until 18:01 UTC while the company monitored stability; the status page said it had identified a likely cause but did not say what it was. Duolingo, Hudl, Strava, Hostinger, Musixmatch and Lovable also reported problems around the same time.

Bitbucket’s own incident page ↗
When
17:22–18:03 UTC
How long
40 min
Incident open on its page
17:22–18:01 UTC
Components affected
13
Bitbucket, 30 days before
2 other outages

What broke when

Major outage
Partial outage
Degraded
Git via HTTPS Website Source downloads Git via SSH API Webhooks Pipelines Email delivery Git LFS Authentication and user management Purchasing & Licensing Signup Packages
UTC 17:1517:3017:4518:00

From Bitbucket’s own status page: when it moved each component into trouble, and back.

At the same time

Started in the hour before or during it

Bitbucket Lovable Hudl Musixmatch Duolingo Strava Hostinger Sentry
UTC 17:0017:3018:00

And 180 lesser-known services. Problems at the same time are a clue, never proof that one caused another.

Timeline

Times in UTC

  1. Investigating
  2. Git via HTTPS: major outage
  3. Website: major outage
  4. Source downloads: major outage
  5. Git via SSH: major outage
  6. API: major outage
  7. Webhooks: major outage
  8. Pipelines: major outage
  9. Email delivery: major outage
  10. Git LFS: major outage
  11. Authentication and user management: major outage
  12. Purchasing & Licensing: major outage
  13. Signup: major outage
  14. Packages: major outage
  15. Git via HTTPS: degraded performance
  16. Website: degraded performance
  17. Source downloads: degraded performance
  18. Git via SSH: degraded performance
  19. API: degraded performance
  20. Webhooks: degraded performance
  21. Pipelines: degraded performance
  22. Email delivery: degraded performance
  23. Git LFS: degraded performance
  24. Authentication and user management: degraded performance
  25. Purchasing & Licensing: degraded performance
  26. Signup: degraded performance
  27. Packages: degraded performance
  28. Fix in place, monitoring
  29. Git via HTTPS: back to normal
  30. Website: back to normal
  31. Source downloads: back to normal
  32. Git via SSH: back to normal
  33. API: back to normal
  34. Webhooks: back to normal
  35. Pipelines: back to normal
  36. Email delivery: back to normal
  37. Git LFS: back to normal
  38. Authentication and user management: back to normal
  39. Purchasing & Licensing: back to normal
  40. Signup: back to normal
  41. Packages: back to normal
  42. Resolved

Where this comes from

Stackpulse reads Bitbucket’s official status page at bitbucket.status.atlassian.com every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.

Stackpulse isn’t affiliated with Bitbucket. Names and logos belong to their owners.

More

Is Bitbucket down right now? · Everything that went down that day · What’s down now