Live / Buildkite / Incident
Buildkite: Small number of incoming GitHub Webhook failing
Buildkite · buildkite.comMinor incidentResolved2026-10-01 06:57 UTC
Public — what happened
Summary
Buildkite said that beginning at 20:52:36 UTC on 30 September 2026, a small share of webhook deliveries from GitHub to Buildkite pipelines were being turned away, meaning the builds those deliveries should have triggered never started. The company noted that GitHub.com users might not get status checks as a result, while GitHub Enterprise Server and other source code providers were unaffected. Buildkite reported at 06:10 UTC on 1 October that it had found the cause, though it did not describe it, and was putting a fix in place. Recovery was seen as the fix rolled out by 06:33 UTC, and the incident was marked resolved at 06:57.
Timeline
- Started — 2026-10-01 06:10 UTC
- Identified — 2026-10-01 06:10 UTC
- Monitoring — 2026-10-01 06:33 UTC
- Resolved — 2026-10-01 06:57 UTC · 47 min after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 41, 2026, our weekly internet health report.