outages.live
Live

OpenCode

OpenCode is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the OpenCode status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks OpenCode since . The days before that show only what OpenCode published.

Incidents in 90 days

22

Days with an incident

6

Median duration

3 min

Longest incident

21 min

Components

6

Console

Console API Operational
90 days ago5 days with an incidentToday
Request logs Operational
90 days ago1 day with an incidentToday

Inference

Inference API Operational
90 days ago3 days with an incidentToday
Go Operational
90 days ago2 days with an incidentToday
Pay-as-you-go Operational
90 days ago2 days with an incidentToday
Free inference Operational
90 days ago2 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Nov 2, 2026

Duration5 min to Console API: Slow responsesDegraded

Oct 31, 2026

Duration5 min to Console API: Elevated error ratesDegraded
Duration3 min to Console API: Elevated error ratesDegraded

Oct 30, 2026

Duration3 min to Console API: Slow responsesDegraded
Duration4 min to Console API: Slow responsesDegraded
Duration20 min to Console API: Slow responsesDegraded
Duration4 min to Console API: Slow responsesDegraded
Duration21 min to Console API: Slow responsesDegraded
Duration4 min to Console API: Slow responsesDegraded
Duration3 min to Console API: Slow responsesDegraded
Duration1 min to Free inference: Intermittent availabilityDegraded
Duration1 min to Pay-as-you-go: Intermittent availabilityDegraded
Duration1 min to Go: Intermittent availabilityDegraded
Duration1 min to Inference API: Intermittent availabilityDegraded

Oct 29, 2026

Duration7 min to Console API: Slow responsesDegraded

Oct 28, 2026

Duration4 min to Console API: Slow responsesDegraded
Duration1 min to Free inference: Elevated error ratesDegraded
Duration1 min to Inference API: Elevated error ratesDegraded

Oct 26, 2026

Duration1 min to Pay-as-you-go: Intermittent availabilityDegraded
Duration1 min to Go: Intermittent availabilityDegraded
Duration1 min to Inference API: Intermittent availabilityDegraded
Duration1 min to Request logs: Intermittent availabilityDegraded

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.

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.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.

RSS
https://outages.live/feed.xml?providers=opencode
Slack
/feed subscribe https://outages.live/feed.xml?providers=opencode

Go from tracking outages to fixing production issues with Polylane.

Try Polylane