- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-central-1
- Down Index
- 31of 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 3d 17h it lasted.
Anything that failed between 2026-03-26 17:47 UTC and 2026-03-30 11:12 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 have been alerted to executors being unavailable in us-central-1 which may cause slow/delayed batch changes or code intel jobs. We are investigating.
provider
- monitoring
A fix has been deployed and we are seeing jobs being available for most customers. You may see a large number of queued jobs but should start decreasing. We are monitoring.
provider
- 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-72baaa2737
Is Sourcegraph still down?
No, this incident was resolved 2026-03-30 11:12 UTC. For Sourcegraph's live state, see https://down.guide/sourcegraph.
How long did it last?
3d 17h, from 2026-03-26 17:47 UTC to 2026-03-30 11:12 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.