Incident Library
Applied filters Root causeCapacity exhaustionComponentPostgreSQL vacuumSymptomIntermittent timeoutsClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. IL-0550 Bitbucket Cloud's database slowed until connection pools saturated and requests timed out, leaving Pipelines pending
    Atlassian2024
    Symptoms

    From 07:22 UTC on 22 February 2024, the bitbucket.org website and the Bitbucket Cloud APIs became slow, and Bitbucket Pipelines runs were badly delayed. Git requests over HTTPS and SSH kept working.

    High latencyConnection pool exhaustionIntermittent timeoutsThroughput degradation
    Root cause
    Capacity exhaustion
    Component
    DatabasePostgreSQL vacuum
    Contributing factor
    No alert on limit
    Remediation
    • Added resources to Bitbucket Pipelines to clear the backlog of jobs, which was fully cleared by 17:30 UTC
    Action items
    • Reconfigure the vacuuming threshold for database tables with high write activity
    • Adjust alert thresholds to catch this behaviour earlier
    • Tune autoscaling and load shedding for the Pipelines services and increase build runner capacity
    View case
Check your cluster for this

This case involves PostgreSQL vacuum and Database. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

Open kubegap

By root cause1

Capacity exhaustion1 case

Component
PostgreSQL vacuumDatabase
Contributing factor
No alert on limit
Organisation
Atlassian
  1. IL-0550 Bitbucket Cloud's database slowed until connection pools saturated and requests timed out, leaving Pipelines pending
    Atlassian2024