outages.live
Live
OpenCodeIncident ·

Pay-as-you-go: Elevated error rates

ResolvedOfficial update
0

OpenCode reported elevated error rates on the Pay-as-you-go component. OpenCode resolved the incident. The outage lasted 2 minutes.

State

Resolved

Started

Lasted

2 min

Worst impact

Degraded

Timeline

2 updates
22:1622:1622:1722:1722:18
DegradedUpdate postedTimes in UTC

Investigating

2 min 100%

Updates

Times in UTC

As posted by OpenCode

Resolved
Investigating

Affected components

1
Pay-as-you-go

OpenCode in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

26

Days with an incident

7

Median duration

3 min

This incident

20% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 min
median 3 min
90 days agoToday

Other OpenCode incidents

All incidents

OpenCode·Inference API: Elevated error rates

The OpenCode Inference API had elevated error rates. OpenCode reports that the incident is resolved. The incident lasted 2 minutes.

Resolved

OpenCode·Free inference: Elevated error rates

OpenCode Free inference had elevated error rates. OpenCode reports that the incident is resolved. The incident lasted 2 minutes.

Resolved

OpenCode·Go: Elevated error rates

OpenCode reported elevated error rates for the Go component. OpenCode resolved the incident. The outage lasted 7 minutes.

Resolved

OpenCode·Console API: Slow responses

Resolved

OpenCode·Console API: Elevated error rates

Resolved

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.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 "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.cc/feed.xml?providers=opencode
Slack
/feed subscribe https://outages.cc/feed.xml?providers=opencode

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane