- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 100
What to do
Check whether your product depends on Sourcegraph. 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 13h 3m it lasted.
Anything that failed between 2026-01-09 02:59 UTC and 2026-01-09 16:02 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 2
- investigating
We are aware of an issue with Batch Changes not correctly publishing in v6.11.2752 and later. This also affects all Sourcegraph Cloud customers. We have found a likely culprit and are working on preparing a patch release.
provider
- resolved
The patch has been applied to all affected Sourcegraph Cloud instances.
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-b7d7c0d439
Is Sourcegraph still down?
No, this incident was resolved 2026-01-09 16:02 UTC. For Sourcegraph's live state, see https://down.guide/sourcegraph.
How long did it last?
13h 3m, from 2026-01-09 02:59 UTC to 2026-01-09 16:02 UTC, by the times Sourcegraph posted.
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.