Loading status…
Sourcegraph status · Developer Tools · checked (45s ago)
Also searched as Cody, Sourcegraph Cody.
No — Sourcegraph is not down. All Sourcegraph systems are reported operational.
According to Sourcegraph's official status page, Sourcegraph was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Sourcegraph's feed reported no outage in 82.27% of our checks.
Everything above is read from Sourcegraph's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Sourcegraph in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Sourcegraph is code search across large codebases, with Cody, its AI assistant, layered on top. It is used both as a hosted service and as a self-managed instance inside a company's own network — a distinction that decides whether this page is relevant to you at all.
The status page covers Sourcegraph's own cloud offering and Cody's hosted backends. A self-hosted or enterprise instance running in your infrastructure is not represented here in any way: if your Sourcegraph lives at a company hostname, its health is your platform team's, and this feed cannot answer for it.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Sourcegraph's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Sourcegraph was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 45s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Sourcegraph's status endpoint.
Sourcegraph has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Sourcegraph posted itself — not every problem users hit.
resolved · Sep 4, 05:33 PM (15d ago)
resolved · Sep 1, 03:34 PM (18d ago)
resolved · Sep 1, 03:31 PM (18d ago)
resolved · Aug 31, 05:56 PM (19d ago)
resolved · Aug 30, 07:10 PM (20d ago)
resolved · Aug 4, 07:25 PM (46d ago)
resolved · Jul 17, 02:30 PM (64d ago)
resolved · Jul 9, 04:00 PM (72d ago)
resolved · May 8, 02:51 AM (135d ago)
resolved · Mar 31, 06:34 PM (172d ago)
resolved · Mar 30, 08:00 AM (173d ago)
resolved · Mar 26, 10:27 PM (177d ago)
resolved · Mar 26, 05:47 PM (177d ago)
resolved · Mar 20, 07:18 PM (183d ago)
resolved · Mar 16, 05:15 PM (187d ago)
resolved · Mar 9, 06:02 PM (194d ago)
resolved · Mar 6, 11:40 AM (197d ago)
resolved · Jan 22, 04:53 PM (240d ago)
resolved · Jan 16, 09:14 PM (246d ago)
resolved · Jan 14, 09:09 PM (248d ago)
Cody depends on upstream model providers, so a Cody failure may be Anthropic's or OpenAI's. Search returning stale or missing results is usually indexing lag on a specific repository rather than an outage — check when that repo last synced. Permissions syncing from your code host can also silently hide results you expect to see.
