- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 1d 7h it lasted.
Anything that failed between 2026-03-30 08:00 UTC and 2026-03-31 15:54 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
- investigating
We noticed one or more issues, and are investigating
provider
- monitoring
We are having issues with one of our upstream providers and are switching traffic to another provider. We are seeing error rates go down and will keep monitoring.
provider
- resolved
The issue has been resolved. We have switched traffic back to our main provider. Users can expect Deep Search to function 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-23bd77b9ef
Is Sourcegraph still down?
No, this incident was resolved 2026-03-31 15:54 UTC. For Sourcegraph's live state, see https://down.guide/sourcegraph.
How long did it last?
1d 7h, from 2026-03-30 08:00 UTC to 2026-03-31 15:54 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.