CodeSandbox
CodeSandbox is operational
Checked just now Operational
History
90 days agoToday
Incidents in 90 days
0
Days with an incident
0
Median duration
No data
Longest incident
No data
Components
5Current status by service
Codesandbox API Operational
90 days agoNo incidentsToday
Codesandbox Website Operational
90 days agoNo incidentsToday
Codesandbox Web Editor Operational
90 days agoNo incidentsToday
Codesandbox CI Operational
90 days agoNo incidentsToday
Codesandbox Clusters
Cluster - fc-us-4 Operational
90 days agoNo incidentsToday
No incident in the last 90 days.
Follow CodeSandbox
Your coding agent knows when CodeSandbox is down, and tells you when a failure is theirs, not yours. You can also get CodeSandbox 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 "codesandbox" and tell me if CodeSandbox 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=codesandboxSlack
/feed subscribe https://outages.cc/feed.xml?providers=codesandboxGo from tracking outages to fixing production issues with Polylane.
Try Polylane