Sourcegraph

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 21:43 UTC

   We're investigating a degradation in [sourcegraph.com/search](http://sourcegraph.com/search "sourcegraph.com/search") public code search performance.

2. resolved 2026-10-20 21:54 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 07:38 UTC

   We're currently seeing increased latency and error rates affecting Sourcegraph Cloud customers in Europe. This is related to an ongoing incident with our underlying Google Cloud infrastructure. Our team is actively monitoring the situation and working with Google Cloud as they...

2. resolved 2026-10-20 17:42 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 19:20 UTC

   We noticed our default code completion model is down and we are investigating

2. resolved 2026-10-02 21:53 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-09-04 17:33 UTC

   We are currently experiencing increased latency and error rates affecting Sourcegraph Cloud. This is related to an ongoing incident with our underlying Google Cloud infrastructure. Our team is actively monitoring the situation and working with Google Cloud as they investigate....

2. resolved 2026-09-09 21:36 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. identified 2026-09-01 15:34 UTC

   We're aware of errors affecting sign-in and authentication for Sourcegraph accounts. This is caused by a Google Cloud networking incident, and we're monitoring for recovery.

2. identified 2026-09-01 15:41 UTC

   The issue has been identified and we're working on a fix

3. monitoring 2026-09-01 16:48 UTC

   Error rates have returned to normal and sign-in has recovered. The underlying Google Cloud networking incident is still ongoing, so we're continuing to monitor closely.

4. resolved 2026-09-02 09:39 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. identified 2026-09-01 15:31 UTC

   Underling Google Cloud infrastructure provider is experiencing performance issues, which might impact Sourcegraph Cloud performance,

2. resolved 2026-09-02 07:55 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-31 17:56 UTC

   We're currently seeing increased latency and error rates affecting Sourcegraph Cloud customers. This is related to an ongoing incident with our underlying Google Cloud infrastructure. Our team is actively monitoring the situation and working with Google Cloud as they...

2. resolved 2026-09-01 08:41 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-30 19:10 UTC

   We noticed increased latency and error rates, investigating.

2. monitoring 2026-08-31 15:22 UTC

   A fix has been deployed and the service is healthy again. We continue to monitor the service.

3. resolved 2026-09-03 08:17 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-04 19:25 UTC

   We are currently experiencing a partial outage affecting Sourcegraph Cloud instances in us-central1 region. Users may be seeing slow response times, failed requests, or reduced functionality across code search, code intelligence, and Cody. We have identified that this incident...

2. identified 2026-08-04 19:34 UTC

   We have identified that this is caused by an ongoing incident with our Cloud provider, Google Cloud Platform. We are actively working to mitigate the issue.

3. resolved 2026-08-06 05:16 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-17 14:30 UTC

   The issue has been identified and we're working on a fix

2. resolved 2026-07-17 16:22 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-09 16:00 UTC

   [analytics.sourcegraph.com](http://analytics.sourcegraph.com "analytics.sourcegraph.com") is currently down for maintenance, and we will provide more updates soon.

2. resolved 2026-07-09 17:37 UTC

   [analytics.sourcegraph.com](http://analytics.sourcegraph.com "analytics.sourcegraph.com") is back up and running.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-08 02:51 UTC

   We’ve identified high error rates affecting Batch Changes on Cloud instances hosted in us-central-1. We have taken remedial action and are seeing queues decrease. We will continue to monitor

2. monitoring 2026-05-08 03:58 UTC

   We continue to see improvement on batch changes queues. We will continue to monitor

3. resolved 2026-05-08 04:41 UTC

   The issue has been resolved. All systems fully operational

4. identified 2026-05-08 12:49 UTC

   The issue is related to Sourcegraph Cloud infrastructure provider, working on mitigation.

5. monitoring 2026-05-08 22:45 UTC

   Impacted instances have been stabilized. We continue to monitor as certain workloads may unexpectedly error out due to unavailability.

6. resolved 2026-05-11 12:48 UTC

   The issue has been resolved on the cloud provider’s side. Batch changes should now operate normally.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 18:34 UTC

   We noticed one or more issues with the [Sourcegraph.com](http://Sourcegraph.com "Sourcegraph.com") MCP servers, and are actively investigating a fix.

2. monitoring 2026-04-01 13:48 UTC

   A fix has been deployed and we're monitoring. We have confirmed the MCP endpoint on [sourcegraph.com](http://sourcegraph.com "sourcegraph.com") working for Claude and Codex

3. resolved 2026-04-01 16:43 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-30 08:00 UTC

   We noticed one or more issues, and are investigating

2. monitoring 2026-03-30 08:25 UTC

   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.

3. resolved 2026-03-31 15:54 UTC

   The issue has been resolved. We have switched traffic back to our main provider. Users can expect Deep Search to function normally.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-26 22:27 UTC

   We noticed issue with our search functionality. Our team is investigating this and we'll share updates soon.

2. monitoring 2026-03-26 23:18 UTC

   We've resolved the issue and search functionality is working now. We're monitoring for any degradation.

3. resolved 2026-03-26 23:25 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-26 17:47 UTC

   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.

2. monitoring 2026-03-26 18:15 UTC

   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.

3. resolved 2026-03-30 11:12 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-03-20 19:18 UTC

   Some Sourcegraph Cloud customers in the Australia (Sydney) region are currently unable to access their instance or are experiencing elevated errors and degraded performance. This is due to an upstream provider outage and we are actively monitoring the situation. We will provide...

2. resolved 2026-03-20 21:18 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude).

1. investigating 2026-03-16 17:15 UTC

   We’re investigating reports of ongoing Google Vertex-Anthropic service issues leading to Sourcegraph instability.

2. monitoring 2026-03-16 17:47 UTC

   All services are healthy. Google Vertex-Anthropic was experiencing issues which led to temporary instability, which we’ve mitigated by rolling traffic over to Anthropic-direct. We continue monitoring the situation and ensuring all services are healthy.

3. resolved 2026-03-18 21:13 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-09 18:02 UTC

   We noticed search performance issues and we are investigating.

2. monitoring 2026-03-09 19:03 UTC

   Performance is back to normal. We’re continuing to monitor it.

3. resolved 2026-03-09 21:53 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-06 11:40 UTC

   The issue with underneath infrastructure has been identified and we’re working on a fix.

2. resolved 2026-03-06 13:01 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 16:53 UTC

   We're investigating reports of issues with self-signed certificates in versions 6.12.x. This may impact login or code host connections for some customers. Updates will be shared as we learn more.

2. identified 2026-01-22 18:00 UTC

   The issue has been identified and we're working on a fix.

3. identified 2026-01-22 22:27 UTC

   The fix is available in [Sourcegraph 6.12.1792](https://sourcegraph.com/changelog/releases/6.12.1792 "Sourcegraph 6.12.1792"). We are currently rolling out this release to Sourcegraph Cloud customers as well.

4. resolved 2026-01-23 07:38 UTC

   The fix is available in [Sourcegraph 6.12.1792](https://sourcegraph.com/changelog/releases/6.12.1792 "Sourcegraph 6.12.1792"). The fix has also been rolled out to all Sourcegraph Cloud customers.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-16 21:14 UTC

   Some Deep Search queries may take longer than expected or get stuck in a loop due to a processing issue. This does not impact availability or usage quota.

2. investigating 2026-01-18 19:01 UTC

   We identified an edge case in how Deep Search processes streaming events. As a precautionary response we have temporarily turned this off for Sourcegraph Cloud customers. This change does not affect Deep Search functionality or results, all features continue to work as expected.

3. investigating 2026-01-20 16:48 UTC

   We've resolved the issue and released a fix in v6.12.1271. This update will automatically roll out to all Cloud customers within the next day.

4. investigating 2026-01-21 15:43 UTC

   The issue has been fully resolved. All Sourcegraph Cloud customers have been upgraded to the patched version. **On-prem customers:** If you're upgrading, please go directly to **v6.12.1287**. See the [changelog](https://sourcegraph.com/changelog/releases) for details.

5. monitoring 2026-01-22 16:54 UTC

   The issue has been fully resolved. All Sourcegraph Cloud customers have been upgraded to the patched version. **On-prem customers:** If you're upgrading, please go directly to **v6.12.1287**. See the [changelog](https://sourcegraph.com/changelog/releases "changelog") for details.

6. resolved 2026-01-22 18:02 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-14 21:09 UTC

   Public code search ([sourcegraph.com/search](http://sourcegraph.com/search "sourcegraph.com/search")) logins are currently unavailable. This outage does not effect Enterprise Starter or Enterprise customers.

2. resolved 2026-01-14 21:46 UTC

   We've resolved the issue.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-09 02:59 UTC

   We are aware of an issue with Batch Changes not correctly publishing in v6.11.2752 and later. This also affects all Sourcegraph Cloud customers. We have found a likely culprit and are working on preparing a patch release.

2. resolved 2026-01-09 16:02 UTC

   The patch has been applied to all affected Sourcegraph Cloud instances.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 08:58 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

2. investigating 2025-12-05 09:00 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

3. monitoring 2025-12-05 09:20 UTC

   Cloudflare identified the issue and implemented a fix, service access is restored. We will continue to monitor.

4. resolved 2025-12-05 09:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Sourcegraph's status page.