Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Users receiving errors when attempting to load BitBucket

Reported by Bitbucket · Developer Tools & CI/CD · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
May 25, 2025, 23:45 UTC
Vendor's clock
Resolved
May 26, 2025, 00:56 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 10 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Bitbucket reports partial outage: "Users receiving errors when attempting to load BitBucket".[E1, E2]
  • The vendor marked it resolved at 2025-05-26 00:56 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-05-26 00:56 UTC · summary s1, evidence 99923017d600f836

Evidence (7)
  1. E1Bitbucket reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Users receiving errors when attempting to load BitBucket". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-05-25 23:45 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-05-26 00:56 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Bitbucket is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. May 25, 2025, 23:45 UTCVendor-reported startVendor time
  2. May 26, 2025, 00:56 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.