Daytona reports normal operation on its official status page.

How often does Daytona have incidents?

Daytona reported 8 incidents in the last 90 days, on 7 different days.

Daytona

Daytona is operational

Checked 2 min ago Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Daytona status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Daytona since Nov 3, 2026. The days before that show only what Daytona published.

Incidents in 90 days

Days with an incident

Median duration

51 min

Longest incident

5 h 56 min

Components

Global

app.daytona.io Operational

90 days ago4 days with an incidentToday

Sandbox

Sandbox creation Operational

90 days ago5 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 30, 2026

Duration5 h 56 min11:58 to 17:53Degraded performance for a subset of US runnersDegraded

All of the nodes in the US Region that were impacted have been fully recovered.status.app.daytona.io

Duration2 h 46 min03:50 to 06:36Sandbox listing (GET /sandbox)Degraded

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.status.app.daytona.io

Oct 29, 2026

Duration30 min16:15 to 16:45US Region Runner DegradationDegraded

All of the nodes in the US Region that were impacted have been fully recoveredstatus.app.daytona.io

Oct 22, 2026

Duration1 h20:45 to 21:45Some feature flags are unavailable in the DashboardDegraded

All services have recoveredstatus.app.daytona.io

Oct 16, 2026

Duration41 min23:12 to 23:53Reduced GPU capacityDegraded

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.status.app.daytona.io

Oct 1, 2026

Duration2 h 3 min11:35 to 13:38Sandbox listing (GET /sandbox)Degraded

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.status.app.daytona.io

Sep 12, 2026

Duration1 min09:00 to 09:00Degraded performanceDegraded

All pending builds have been completed and the issue is resolved, we are adding additional safeguards and better alerting to make sure the builder queue is more reliable.status.app.daytona.io

Sep 4, 2026

Duration4 min13:41 to 13:45Elevated errors on sandbox creationDegraded

This incident has been resolved. Error rates on sandbox creation have returned to normal levels and all services are operating as expected. Thank you for your patience.status.app.daytona.io

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.

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 "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.

RSS

https://outages.cc/feed.xml?providers=daytona

Slack

/feed subscribe https://outages.cc/feed.xml?providers=daytona

Go from tracking outages to fixing production issues with Polylane.

Try Polylane