Live  /  Buildkite  /  Incident

Buildkite: Delayed notifications

Buildkite · buildkite.comMinor incidentResolved2026-10-20 21:05 UTC
Public — what happened

Summary

Buildkite said that starting at 19:57 UTC on 2026-10-20, some customers were receiving their build and job notifications late. By 20:15 UTC the company said it had found the problem, added extra capacity, and that notification delays were back to normal while it watched for stability. The incident, which Buildkite rated minor, was marked resolved at 21:05 UTC.

Affected

GitHub Commit Status Notifications, Email Notifications, Slack Notifications, Webhook Notifications

As listed on Buildkite’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Buildkite against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Buildkite: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Buildkite report →

More from Buildkite

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Buildkite status & history page.

Related: Buildkite status & history. SquidGrid is not affiliated with Buildkite.