Go: Elevated error rates
OpenCode reports elevated error rates on the Go component. OpenCode says the incident is resolved. It lasted one minute.
State
Resolved
Started
Lasted
1 min
Worst impact
Degraded
Timeline
2 updatesResolved
1 min 100%
Updates
Times in UTCAs posted by OpenCode
Affected components
1OpenCode in the last 90 days
Full historyIncidents in 90 days
39
Days with an incident
12
Median duration
1 min
This incident
About the median
Other OpenCode incidents
All incidentsOpenCode·Pay-as-you-go: Elevated error rates
Pay-as-you-go had elevated error rates on OpenCode. OpenCode reports that the incident is resolved. It lasted 1 minute.
OpenCode·Free inference: Elevated error rates
Free inference on OpenCode had elevated error rates. OpenCode reports that the incident is resolved. It lasted 1 minute.
OpenCode·Inference API: Elevated error rates
The OpenCode Inference API had elevated error rates. OpenCode reports that this incident is resolved and it lasted 1 minute.
OpenCode·Request logs: Intermittent availability
OpenCode Request logs had intermittent availability problems. OpenCode reports that the incident is resolved. The incident lasted 1 minute.
OpenCode·Request logs: Intermittent availability
OpenCode Request logs had intermittent availability and were degraded. OpenCode reports that this incident is resolved. The outage lasted 1 minute.
Follow OpenCode
Your coding agent knows when OpenCode is down, and tells you when a failure is theirs, not yours. You can also get OpenCode 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.live/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 "opencode" and tell me if OpenCode 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.live/feed.xml?providers=opencode/feed subscribe https://outages.live/feed.xml?providers=opencodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane