If you encounter a launching failure when “Run Workflow” from your own cloud saved workflow, please try the following,
| Machine Size | Status | Remarks |
|---|---|---|
| Free(CPU) | Operational | |
| Medium | Operational | |
| Large | Operational | |
| Extra Large | Operational | |
| 2X Large | Operational | |
| 2XL Plus | Operational | Limited supply, please try 2x large if failed. |
| Maintenance | Updates |
|---|---|
| 2025-02-24 06:30AM UTC | Done. Machine launching back to normal. |
| 2025-02-24 06:00AM UTC | We will stop machine launching for about 30mins to update core infrastructure. Your running machines will not be affected during the update. |
| Incident | Updates |
|---|---|
| 2025-02-06 9:20 UTC | Machine Launchings are back online. Monitoring. |
| 2025-02-06 9:00 UTC | Underlying storage provider major incident, we are working with them to bring back the services. |
| 2025-02-06 8:20 UTC | Launching failed. Our engineers are investigating |
| Maintenance | Updates |
|---|---|
| 2025-01-22 08:30AM UTC | Update finished. |
| 2025-01-22 08:00AM UTC | Update in progress. |
| 2025-01-22 06:30AM UTC | We will update in 1 hour. |
| 2025-01-22 06:00AM UTC | We are postponing this update a bit later. Will post back once we know the time. |
| 2025-01-22 05:00AM UTC | We will stop the machine launching and “Add Funds” / Subscription for about 2 hours to update our core infrastructure. Your running machines will not be affected during the update. |
| Incident | Updates |
|---|---|
| 2024-01-17 19:40 UTC | We applied a fix and machine launching are back to normal. Monitoring. |
| 2024-01-17 19:04 UTC | Still Investigating. |
| 2025-01-17 18:00 UTC | Launching failed. Our engineers are investigating |
| Incident | Updates |
|---|---|
| 2024-01-06 18:00 UTC | Back to normal. |
| 2024-01-06 17:04 UTC | Most launches are successful now. Please relaunch if failed. |
| 2024-01-06 16:46 UTC | Please relaunch if failed. Should be working now. |
| 2024-01-06 16:36 UTC | Found a temp fix, patch applied. |
| 2024-01-06 16:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-12-05 00:04 UTC | Machine launching back to normal. |
| 2024-12-04 23:00 UTC | We are investigating. Underlying storage issue. |
| 2024-12-04 18:00 UTC | Launching failed. |
| Incident | Updates |
|---|---|
| 2024-11-29 04:30 UTC | Launching is stable now. Monitoring. |
| 2024-11-29 02:30 UTC | Our network upstream provider is having a major outage, we are engaging with them to have a quick fix. |
| 2024-11-29 01:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-11-27 15:50 UTC | Launching is stable now. Monitoring. |
| 2024-11-27 14:43 UTC | https://www.cloudflarestatus.com/ Cloudflare is investigating delays in propagation of updates to DNS records. Please relaunch if failed. |
| 2024-11-27 14:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-11-12 04:30 UTC | Back to normal with intermittent failures. |
| 2024-11-12 04:10 UTC | Still working on a fix. |
| 2024-11-12 02:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-11-11 14:28 UTC | Back to normal. |
| 2024-11-11 14:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-11-4 08:30 UTC | Back to normal, working on a fix to prevent future failures. |
| 2024-11-4 07:30 UTC | Launching is failing intermittently. Still working on a fix. |
| 2024-11-4 06:00 UTC | Launching failed. Our engineers are investigating. |
| Incident | Updates |
|---|---|
| 2024-10-14 21:00 UTC | Launching back to normal. Backend component connection issue. |
| 2024-10-14 20:44 UTC | Investigating and working on a fix. |
| 2024-10-14 19:48 UTC | Launching failed. |