Major outage
Daytona reports a major outage on app.daytona.io. The outage is resolved. It lasted 12 minutes.
State
Resolved
Started
Lasted
12 min
Worst impact
Major outage
Timeline
2 updatesComponents degraded
12 min 100%
Updates
Times in UTCAs posted by Daytona
Affected components
1Daytona in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
10
Median duration
30 min
This incident
60% shorter than the median
Other Daytona incidents
All incidents
Daytona·Degradation of Creations and API Operations
Daytona reports that sandbox creation on app.daytona.io does not work correctly. Daytona is investigating the incident. The problem started 47 minutes ago.

Daytona·Major outage
Daytona reports a major outage on app.daytona.io. Daytona says that the incident is resolved. The outage lasted 3 minutes.

Daytona·Major outage
Daytona reports a major outage on app.daytona.io. The incident is resolved. It lasted 6 minutes.

Daytona·Major outage
Daytona reports a major outage on app.daytona.io. The incident is resolved. It lasted 9 minutes.

Daytona·Degraded performance: API and sandbox operations
Daytona reported degraded performance on app.daytona.io and sandbox creation. Some API requests and sandbox create, start, stop, and delete operations were slow or timed out. Daytona resolved the incident, which lasted about 103 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