Outage
Daytona reports a major outage that affects app.daytona.io and sandbox creation. The provider has identified the issue and works on a fix. Some services show recovery. The incident started 46 minutes ago and continues.
State
Degraded
Started
Ongoing for
50 min
Worst impact
Major outage
Timeline
3 updatesDowntime
45 min 90%
Degraded
5 min 10%
Updates
Times in UTCAs posted by Daytona
The team has identified the issue and is actively working on a resolution. Some services are seeing recovery.
Services have been taken down while the team investigates the issue
The team is currently investigating an outage
Affected components
2Daytona in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
11
Median duration
11 min
This incident
4.8× the median
Other Daytona incidents
All incidents
Daytona·Major outage
Daytona reports a major outage on app.daytona.io. The incident is resolved. It lasted 9 minutes.
Daytona·Major outage
Daytona reports a major outage that affects app.daytona.io. Daytona reports that the incident is resolved. The outage lasted 3 minutes.
Daytona·Major outage
Daytona reports that app.daytona.io did not work during a major outage. The incident is resolved and it lasted 3 minutes.
Daytona·Major outage
Daytona reports a major outage that affects app.daytona.io. Daytona resolved the outage after 3 minutes.
Daytona·Major outage
Daytona reports a major outage on app.daytona.io. The outage is resolved. It lasted 12 minutes.
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