rewindex

CompaniesBuildkiteIncidents

Buildkite: Delayed Outbound Notifications

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatewww.buildkitestatus.com (opens in new tab)

Timeline of updates

  1. resolved

    We've seen an increase in notification delivery latency up to 9 minutes since 05:33 UTC. This was caused by insufficient capacity in our notifications queue during this period. Autoscaling was paused to stabilise our existing capacity while migrating traffic between capacity groups.

From Buildkite’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on www.buildkitestatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Buildkite, started 2023-07-25 05:30 UTC, resolved after 0 min, 1 update(s).

Title
Delayed Outbound Notifications
Vendor
Buildkite
Date
URL
https://rewindex.com/company/buildkite/incidents/jk86138ldvzj

Buildkite profileRecent Buildkite incidentsAll outages on July 25, 2023Buildkite in July 2023MarkdownJSON