Sandbox listing (GET /sandbox)
This issue has been resolved. All sandboxes, including those created during the incident, are now correctly returned in list results. The issue was caused by a disruption in the internal service responsible for indexing sandbox data. The underlying cause has been addressed, and we have taken steps to prevent a recurrence. We apologize for any inconvenience this may have caused.
The latest update from Daytona.
State
Resolved
Started
33 d ago
2026-10-01 11:35 UTC
Lasted
2 h 3 min
until 2026-10-01 13:38 UTC
Worst impact
Degraded
Timeline
2 updatesDegraded
2 h 3 min 100%
Updates
Times in UTCAs posted by Daytona
This issue has been resolved. All sandboxes, including those created during the incident, are now correctly returned in list results. The issue was caused by a disruption in the internal service responsible for indexing sandbox data. The underlying cause has been addressed, and we have taken steps to prevent a recurrence. We apologize for any inconvenience this may have caused.
Since 11:35 UTC, sandboxes created after this time are not being returned by the sandbox list endpoint (GET /sandbox). Sandbox creation and direct lookups are unaffected. We have identified the cause and are working on a fix. We will provide another update shortly.
Affected components
1Daytona in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
7
Median duration
51 min
This incident
2.4× the median
Other Daytona incidents
All incidents
Daytona·Degraded performance for a subset of US runners
All of the nodes in the US Region that were impacted have been fully recovered.
Daytona·Sandbox listing (GET /sandbox)
An issue in our data indexing pipeline delayed updates to the sandbox list between 22:42 UTC on October 29 and 06:30 UTC on October 30, so recently created, changed or deleted sandboxes may not have appeared correctly in list results during that time. Sandbox operations themselves were not affected, and no data was lost. The pipeline has been restored, all pending updates have been processed, and the sandbox list is now fully up to date.
Daytona·US Region Runner Degradation
All of the nodes in the US Region that were impacted have been fully recovered
Daytona·Some feature flags are unavailable in the Dashboard
All services have recovered
Daytona·Reduced GPU capacity
Between 23:12 and 23:53 UTC on October 16, part of our H100 and RTX PRO 6000 capacity was unavailable due to an issue at one of our infrastructure providers. Capacity has been fully restored.
Follow Daytona
Your coding agent knows when Daytona is down, and tells you when a failure is theirs, not yours. You can also get Daytona 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 "daytona" and tell me if Daytona 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=daytona/feed subscribe https://outages.live/feed.xml?providers=daytonaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane