outages.live
Live

Sourcegraph

Sourcegraph is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

17

Median duration

18 h 6 min

Longest incident

5 days

Components

8
Sourcegraph Cloud Operational
90 days agoNo incidentsToday
Sourcegraph self-hosted release (latest) Operational
90 days agoNo incidentsToday
Sourcegraph Model Provider Operational
90 days agoNo incidentsToday
Sourcegraph Accounts Operational
90 days agoNo incidentsToday
Sourcegraph Workspaces Operational
90 days agoNo incidentsToday
Sourcegraph Analytics Operational
90 days agoNo incidentsToday
Sourcegraph Enterprise Portal Operational
90 days agoNo incidentsToday
Sourcegraph.com public code search Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration11 min21:43 to 21:54Sourcegraph.com public code search issuesDegraded

The issue has been resolved

Duration10 h 4 min07:38 to 17:42Sourcegraph Cloud is degraded in Europe regionDegraded

The issue has been resolved

Oct 1, 2026

Duration26 h 33 min19:20 to 21:53Code completion for Cody is unavailableNotice

The issue has been resolved

Sep 4, 2026

Duration5 days17:33 to 21:36Sourcegraph Cloud is degraded in US Central regionPartial outage

The issue has been resolved

Sep 1, 2026

Duration18 h 6 min15:34 to 09:39Sign-in and authentication errorsPartial outage

The issue has been resolved

Duration16 h 24 min15:31 to 07:55Cloud customers might see degraded performance because of underling Google Platform issuesDegraded

The issue has been resolved

Aug 31, 2026

Duration14 h 45 min17:56 to 08:41Sourcegraph Cloud is experiencing elevated errorDegraded

The issue has been resolved.

Aug 30, 2026

Duration4 days19:10 to 08:17Sourcegraph.com public code search degradedDegraded

The issue has been resolved

Aug 4, 2026

Duration33 h 51 min19:25 to 05:16Partial outage across Cloud instancesDegraded

The issue has been resolved

Follow Sourcegraph

Your coding agent knows when Sourcegraph is down, and tells you when a failure is theirs, not yours. You can also get Sourcegraph incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sourcegraph" and tell me if Sourcegraph has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=sourcegraph
Slack
/feed subscribe https://outages.cc/feed.xml?providers=sourcegraph

Go from tracking outages to fixing production issues with Polylane.

Try Polylane