Partial outage across Cloud instances
The issue has been resolved
The latest update from Sourcegraph.
State
Resolved
Started
89 d ago
2026-08-04 19:25 UTC
Lasted
33 h 51 min
until 2026-08-06 05:16 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
9 min 0%
Identified
33 h 42 min 100%
Updates
Times in UTCAs posted by Sourcegraph
The issue has been resolved
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.
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 is related to compute capacity constraints in our Google Cloud Platform infrastructure. We are actively working to mitigate the issue.
Sourcegraph in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
17
Median duration
18 h 6 min
This incident
1.9× the median
Other Sourcegraph incidents
All incidentsSourcegraph·Sourcegraph.com public code search issues
The issue has been resolved
Sourcegraph·Sourcegraph Cloud is degraded in Europe region
The issue has been resolved
Sourcegraph·Code completion for Cody is unavailable
The issue has been resolved
Sourcegraph·Sourcegraph Cloud is degraded in US Central region
The issue has been resolved
Sourcegraph·Sign-in and authentication errors
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.
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.
https://outages.cc/feed.xml?providers=sourcegraph/feed subscribe https://outages.cc/feed.xml?providers=sourcegraphFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane