Skip to main content
Sourcegraph

Partial outage across Cloud instances

Degraded Lasted 1d 9h · started · Sourcegraph's page

Level
confirmed
Worst impact
Degraded
Regions
us, us-central1
Down Index
31of 100

What to do

  • Check whether you use Sourcegraph in us, us-central1. 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 1d 9h it lasted.

    Anything that failed between 2026-08-04 19:25 UTC and 2026-08-06 05:16 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 3

  1. investigating

    We are currently experiencing a partial outage affecting Sourcegraph Cloud instances in us-central1 region. Users may be seeing slow response times, failed requests, or reduced functionality across code search, code intelligence, and Cody. We have identified that this incident is related to compute capacity constraints in our Google Cloud Platform infrastructure. We are actively working to mitigate the issue.

    provider

  2. identified

    We have identified that this is caused by an ongoing incident with our Cloud provider, Google Cloud Platform. We are actively working to mitigate the issue.

    provider

  3. resolved

    The issue has been 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-8f604d6626

Is Sourcegraph still down?

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

How long did it last?

1d 9h, from 2026-08-04 19:25 UTC to 2026-08-06 05:16 UTC, by the times Sourcegraph posted.

What was affected?

Sourcegraph named in us, us-central1.

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.