Region-by-region timeline
When each monitored region started failing and when it recovered, per RealUptime's own probes. A region not listed here never failed during this incident.
Australia4h
Failing from Sep 13, 2026, 2:04 PM UTC, recovered Sep 13, 2026, 6:04 PM UTC
South America4h 20m
Failing from Sep 13, 2026, 1:43 PM UTC, recovered Sep 13, 2026, 6:03 PM UTC
What failed, by surface
Bitbucket exposes more than one surface we probe separately. This breaks the same incident down by which surface failed, in which region, and when.
Web
Australia: failing from Sep 13, 2026, 2:04 PM UTC, recovered Sep 13, 2026, 6:04 PM UTCSouth America: failing from Sep 13, 2026, 1:43 PM UTC, recovered Sep 13, 2026, 6:03 PM UTC
API
Australia: failing from Sep 13, 2026, 2:04 PM UTC, recovered Sep 13, 2026, 6:04 PM UTCSouth America: failing from Sep 13, 2026, 1:43 PM UTC, recovered Sep 13, 2026, 6:03 PM UTC
How this was measured
This record comes only from RealUptime's own scheduled probes against Bitbucket's public, unauthenticated endpoints, run from 10 named regions. It is never built from user reports or from Bitbucket's own status page, and it does not change once this incident closes: this page is the permanent record, not a live view.
See Bitbucket's full evidence record or read the methodology.