- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 39of 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 49m it lasted.
Anything that failed between 2025-12-05 08:58 UTC and 2025-12-05 09:47 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 4
- investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
provider
- investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
provider
- monitoring
Cloudflare identified the issue and implemented a fix, service access is restored. We will continue to monitor.
provider
- resolved
This incident 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-430ca2aeb3
Is Sourcegraph still down?
No, this incident was resolved 2025-12-05 09:47 UTC. For Sourcegraph's live state, see https://down.guide/sourcegraph.
How long did it last?
49m, from 2025-12-05 08:58 UTC to 2025-12-05 09:47 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.