Sourcegraph Outage History
28 incidents recorded over the last 365 days, 28 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Sourcegraph Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 4, 2026 | Partial outage across Cloud instancesThe issue has been resolved | 33h 51m | Resolved |
| Jul 17, 2026 | Cloud executors might experience performance issues. This can impact auto indexing and batch changes jobs not being processed imediatelly.The issue has been resolved | 1h 51m | Resolved |
| Jul 9, 2026 | Analytics Maintenance[analytics.sourcegraph.com](http://analytics.sourcegraph.com "analytics.sourcegraph.com") is back up and running. | 1h 37m | Resolved |
| May 8, 2026 | Batch Changes errors on us-central-1 Cloud instancesThe issue has been resolved on the cloud provider’s side. Batch changes should now operate normally. | 1h 49m | Resolved |
| Mar 31, 2026 | Sourcegraph.com MCP Server issuesThe issue has been resolved | 22h 9m | Resolved |
| Mar 30, 2026 | Deep Searching failing with resource exhaustedThe issue has been resolved. We have switched traffic back to our main provider. Users can expect Deep Search to function normally. | 31h 53m | Resolved |
| Mar 26, 2026 | Search functionality is UnavailableThe issue has been resolved. | 58 min | Resolved |
| Mar 26, 2026 | Executor unavailability in us-central-1 cloud instancesThe issue has been resolved | 89h 24m | Resolved |
| Mar 20, 2026 | Service disruption for Sourcegraph Cloud instances in Australia (Sydney)The issue has been resolved | 1h 59m | Resolved |
| Mar 16, 2026 | Google Vertex-Anthropic service issuesThe issue has been resolved. | 51h 58m | Resolved |
| Mar 9, 2026 | Degraded search performance on public code search sourcegraph.comThe issue has been resolved | 3h 50m | Resolved |
| Mar 6, 2026 | Batch changes and code intel updates migh be degraded in the specific regions incl. Australia and Japan.The issue has been resolved. | 1h 21m | Resolved |
| Jan 22, 2026 | Issues with self-signed certificate configurationThe 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. | 14h 45m | Resolved |
| Jan 16, 2026 | Degraded Deep Search performanceThe issue has been resolved | 140h 48m | Resolved |
| Jan 14, 2026 | Public code search login unavailableWe've resolved the issue. | 36 min | Resolved |
| Jan 9, 2026 | Issues with Batch Changes publishingThe patch has been applied to all affected Sourcegraph Cloud instances. | 13h 3m | Resolved |
| Dec 5, 2025 | Internal Server Errors returned for several servicesThis incident has been resolved. | 49 min | Resolved |
| Nov 28, 2025 | This is an example incidentWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on. | -2339293 min | Resolved |
| Nov 28, 2025 | this is a test alert for status pagewe tried everything and learned nothing | -2332079 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] http health check for https://sorcegraph.com/This incident has been resolved. | -2317779 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] prometheus: less than 90% percentage pods available for 10m0sThis incident has been resolved. | -2308921 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] frontend: 1+ critical test alert metricThis incident has been resolved. | -2319523 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] frontend: 1+ critical test alert metricThis incident has been resolved. | -2319496 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] http health check for https://sorcegraph.com/This incident has been resolved. | -2317927 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] http health check for https://sorcegraph.com/This incident has been resolved. | -2317893 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] http health check for https://sourcegraph.com/pricingThis incident has been resolved. | -2301451 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] http health check for https://sourcegraph.com/Testing alerts | -2303226 min | Resolved |
| Nov 28, 2025 | [Cloud] [CRITICAL] prometheus: less than 90% percentage pods available for 10m0sThis incident has been resolved. | -2308722 min | Resolved |
How to Read This Sourcegraph Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Sourcegraph acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Sourcegraph outage in this window ran 5d 20h, against a mean recovery of 1d. If you depend on Sourcegraph in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.