Skip to main content
Buildkite

Auth failures with remote MCP server

Degraded Lasted 1h 40m · started · Buildkite's page

Level
confirmed
Worst impact
Degraded
Down Index
19of 100

What to do

  • Check whether your product depends on Buildkite. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 40m it lasted.

    Anything that failed between 2026-04-22 21:19 UTC and 2026-04-22 22:59 UTC may need a replay.
  • Subscribe to Buildkite's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=buildkite works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Buildkite 4

  1. investigating

    We are currently investigating reports of authentication failures with the remote MCP server.

    provider

  2. investigating

    We are continuing to investigate errors when authenticating to the remote MCP server.

    provider

  3. monitoring

    We have rolled back a change on the remote MCP server that was contributing to authentication failures.

    provider

  4. resolved

    The issue is resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-7aec4e3894

Is Buildkite still down?

No, this incident was resolved 2026-04-22 22:59 UTC. For Buildkite's live state, see https://down.guide/buildkite.

How long did it last?

1h 40m, from 2026-04-22 21:19 UTC to 2026-04-22 22:59 UTC, by the times Buildkite posted.

What caused it?

Buildkite hasn't published a root cause. If it does, it shows here.

Where does this come from?

Buildkite's official status page, https://www.buildkitestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.