Skip to main content
Vendor reliability

Vendor record

Buildkite

Vendor reports Operational

Checked

Front door check counts and Buildkite’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Buildkite endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.buildkite.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Buildkite product, region or your app worked.

How we count front door checks

Buildkite says

Incident posts from Buildkite’s status page, with its titles, impact levels and times. They say what Buildkite chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

35

incidents Buildkite posted, last 180 days

Median recorded duration: 1h 19m. From 35 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Degraded checkout performance with Hosted Agents

    Minor

    Started, per Buildkite

    Closed in our record(5h 41m)

    Buildkite’s post
  • Small number of incoming GitHub Webhook failing

    Minor

    Started, per Buildkite

    Closed in our record(1h)

    Buildkite’s post
  • Delayed notifications

    Minor

    Started, per Buildkite

    Closed in our record(1h 36m)

    Buildkite’s post
  • Issues with webhook ingestion, GraphQL queries

    Minor

    Started, per Buildkite

    Closed in our record(53m)

    Buildkite’s post
  • AWS us-east-1 outage

    Not specified

    Started, per Buildkite

    Closed in our record(52m)

    Buildkite’s post
15 older records
  • Increased latency and error rates

    Minor

    Started, per Buildkite

    Closed in our record(1h 14m)

    Buildkite’s post
  • Buildkite service disruption

    Major

    Started, per Buildkite

    Closed in our record(6h 47m)

    Buildkite’s post
  • Hosted Agents - Increased latency and error rates

    Minor

    Started, per Buildkite

    Closed in our record(57m)

    Buildkite’s post
  • Increased latency and error rates

    Major

    Started, per Buildkite

    Closed in our record(9m)

  • Scheduling delay for hosted agents

    Minor

    Started, per Buildkite

    Closed in our record(1h 9m)

    Buildkite’s post
  • Delays in Hosted Agents job dispatch

    Minor

    Started, per Buildkite

    Closed in our record(1h 9m)

    Buildkite’s post
  • Delivery issues with email notifications

    Minor

    Started, per Buildkite

    Closed in our record(1h 27m)

    Buildkite’s post
  • Test Engine ingestion delayed, catching up

    Minor

    Started, per Buildkite

    Closed in our record(54m)

    Buildkite’s post
  • Issues identified with buildkite-agent registration

    Minor

    Started, per Buildkite

    Closed in our record(1h 37m)

    Buildkite’s post
  • Buildkite service disruption

    Major

    Started, per Buildkite

    Closed in our record(1h 30m)

    Buildkite’s post
  • Unexpected agent disconnection for some customers

    Minor

    Started, per Buildkite

    Closed in our record(1h 38m)

    Buildkite’s post
  • Buildkite service disruption

    Minor

    Started, per Buildkite

    Closed in our record(2h 3m)

    Buildkite’s post
  • Slow web UI

    Minor

    Started, per Buildkite

    Closed in our record(1h 8m)

    Buildkite’s post
  • Buildkite service disruption

    Minor

    Started, per Buildkite

    Closed in our record(1h 26m)

    Buildkite’s post
  • Slow web UI

    Minor

    Started, per Buildkite

    Closed in our record(3h 9m)

    Buildkite’s post

Your code, your dependencies

See which of your code paths call Buildkite

Connect GitHub or GitLab to find where your public or private repository uses Buildkite. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Buildkite status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · BuildkiteStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/buildkite?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Buildkite status badge"></iframe>

Frequently Asked Questions

Is Buildkite currently down?

Buildkite's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Buildkite last have an outage?

The most recent closed incident record began 9 days ago and spans 5h 41m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Buildkite?

No. CheckUpstream checks Buildkite’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Buildkite in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Buildkite?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.