State
Resolved
Started
Lasted
4 min
Worst impact
Degraded
Timeline
0 updates15:0315:0415:0515:0615:07
DegradedUpdate postedTimes in UTC
Resolved
4 min 100%
Updates
Times in UTCNo update text yet.
Affected components
1Console API
OpenCode in the last 90 days
Full history90 days agoToday
Incidents in 90 days
22
Days with an incident
6
Median duration
3 min
This incident
1.3× the median
Other OpenCode incidents
All incidentsFollow 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=opencodeSlack
/feed subscribe https://outages.live/feed.xml?providers=opencodeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane