Skip to main content
Sourcegraph

Batch Changes errors on us-central-1 Cloud instances

Degraded Lasted 1h 49m · started · Sourcegraph's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-central-1
Down Index
27of 100

What to do

  • Check whether you use Sourcegraph in us, us-central-1. 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 49m it lasted.

    Anything that failed between 2026-05-08 02:51 UTC and 2026-05-08 04:41 UTC may need a replay.
  • Subscribe to Sourcegraph's feed to hear about the next one first. RSS feed

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

Updates from Sourcegraph 6

  1. monitoring

    We’ve identified high error rates affecting Batch Changes on Cloud instances hosted in us-central-1. We have taken remedial action and are seeing queues decrease. We will continue to monitor

    provider

  2. monitoring

    We continue to see improvement on batch changes queues. We will continue to monitor

    provider

  3. resolved

    The issue has been resolved. All systems fully operational

    provider

  4. identified

    The issue is related to Sourcegraph Cloud infrastructure provider, working on mitigation.

    provider

  5. monitoring

    Impacted instances have been stabilized. We continue to monitor as certain workloads may unexpectedly error out due to unavailability.

    provider

  6. resolved

    The issue has been resolved on the cloud provider’s side. Batch changes should now operate normally.

    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-a437fdb65d

Is Sourcegraph still down?

No, this incident was resolved 2026-05-08 04:41 UTC. For Sourcegraph's live state, see https://down.guide/sourcegraph.

How long did it last?

1h 49m, from 2026-05-08 02:51 UTC to 2026-05-08 04:41 UTC, by the times Sourcegraph posted.

What was affected?

Sourcegraph named in us, us-central-1.

What caused it?

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

Where does this come from?

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