Type: Incident Affected Components: Washington, D.C. - WAS Sep 15, 07:16:19 GMT+0 - Identified - We are working with our provider to resolve this issue as soon as possible. In the meantime you can switch to some other instance type like A100/H100/H200.
Type: Incident Duration: 5 hours Affected Components: Singapore - SIN Sep 11, 02:00:00 GMT+0 - Investigating - Customers located in Asia are reporting an elevated rate of 404 when contacting their service. Sep 11, 07:00:00 GMT+0 - Resolved - This incident has been resolved. A crash on the load balancer stack caused some network propagation issue.
Type: Incident Duration: 20 minutes Affected Components: Build / Provisioning Sep 8, 07:05:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 8, 07:25:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 2 minutes Affected Components: API, Control Panel Jul 23, 15:16:00 GMT+0 - Investigating - We are investigating this issue. Existing deployments are working not affected. Jul 23, 15:17:51 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 59 minutes Affected Components: Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN, Frankfurt - FRA Jul 21, 09:30:00 GMT+0 - Investigating - We had an issue where redeploying a service using a custom domain would result in the domain returning 404\. Existing deployments were unaffected Jul 21, 11:29:00 GMT+0 - Resolved - This incident has been resolv…
Type: Incident Duration: 5 hours and 30 minutes Affected Components: Build / Provisioning Jul 20, 22:30:00 GMT+0 - Investigating - New deployments were throttled, causing them to take up to 20-30 minutes to reach a Healthy state. Existing deployments unaffected Jul 21, 04:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Affected Components: Control Panel Jul 16, 08:59:54 GMT+0 - Identified - The upstream provider we use for authentication is going through a major incident. Login attempts to the control panel are failing. Direct API usage through tokens is working as expected and the running workloads are not affected.
Type: Incident Duration: 27 minutes Affected Components: Build / Provisioning Jun 26, 23:00:00 GMT+0 - Investigating - Jun 27, 01:44:40 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 11 minutes Affected Components: Paris - PAR, Frankfurt - FRA Jun 23, 14:08:37 GMT+0 - Investigating - We are currently investigating this incident. Jun 23, 14:13:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 23, 14:19:14 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 29 minutes Affected Components: Paris - PAR Jun 22, 09:05:46 GMT+0 - Investigating - We are currently investigating this incident. Jun 22, 09:16:49 GMT+0 - Investigating - We are currently investigating this incident. Other regions are healthy. As a workaround, redeploy to Frankfurt or any other region. Jun 22, 09:34:53 GMT+0 - Resolved - This incident has been resolved. H…
Type: Incident Duration: 6 hours and 9 minutes Affected Components: San Francisco - SFO, Paris - PAR, Washington, D.C. - WAS, Frankfurt - FRA Jun 16, 11:50:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 16, 12:22:23 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 16, 15:34:17 GMT+0 - Identified - We are continuing to work on a fix for th…
Type: Incident Duration: 3 hours and 9 minutes Jun 15, 08:25:00 GMT+0 - Investigating - We are currently investigating this incident. Jun 15, 09:53:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 15, 10:12:07 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 15, 11:34:22 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 2 hours and 7 minutes Affected Components: Build / Provisioning Jun 5, 18:12:10 GMT+0 - Investigating - We are currently investigating this incident. Jun 5, 18:38:17 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 2 hours and 2 minutes Affected Components: Build / Provisioning Jun 1, 14:26:01 GMT+0 - Identified - Related status Jun 1, 16:27:34 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 48 minutes Affected Components: Build / Provisioning Jun 1, 11:31:46 GMT+0 - Identified - We have identified an outage with our database provider. Database operations might fail in the mean time. Jun 1, 12:19:26 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 18 hours and 24 minutes Affected Components: Frankfurt - FRA May 27, 13:11:30 GMT+0 - Resolved - This incident has been resolved. May 26, 18:47:22 GMT+0 - Identified - We are investigating the possible loss of an hypervisor node. We will update you as soon as we have more information.
Type: Incident Duration: 21 hours and 22 minutes Affected Components: Frankfurt - FRA May 25, 13:04:03 GMT+0 - Identified - We are continuing to work on a fix for this incident, the volumes on this hypervisor (acd25f48-54b7-f945-dd96-ad33b0efabc2) are currently not accessible. May 26, 10:25:41 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 4 hours and 23 minutes Affected Components: Build / Provisioning May 14, 22:32:18 GMT+0 - Investigating - We are currently investigating this incident. May 14, 22:50:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 15, 02:17:00 GMT+0 - Identified - Most regions are back to normal, but Tokyo is still lagging behind. We are still working on a…
Type: Incident Duration: 2 hours and 2 minutes Affected Components: Build / Provisioning May 11, 13:41:59 GMT+0 - Investigating - We are currently investigating this incident. May 11, 14:12:37 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 11, 15:43:43 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 15 minutes Affected Components: Build / Provisioning, Washington, D.C. - WAS May 5, 16:20:00 GMT+0 - Investigating - We are currently investigating this incident. May 5, 16:35:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 16 hours and 20 minutes Affected Components: Tokyo - TYO, Build / Provisioning, Singapore - SIN May 4, 22:50:00 GMT+0 - Resolved - This incident has been resolved. May 4, 06:30:00 GMT+0 - Investigating - We are currently investigating this incident. May 4, 07:50:36 GMT+0 - Identified - Provisioning for all regions is now back to normal, we're still investigating delays in…
Type: Incident Duration: 20 hours Affected Components: Frankfurt - FRA May 3, 16:30:00 GMT+0 - Investigating - We are currently investigating this incident. May 3, 16:50:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 4 minutes Affected Components: Build / Provisioning Apr 29, 11:46:32 GMT+0 - Investigating - We are currently investigating this incident. Apr 29, 11:49:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 29, 11:50:53 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 23 minutes Affected Components: Build / Provisioning Apr 27, 07:30:00 GMT+0 - Identified - We noticed some delay in provisioning and wake up. We are continuing to work on a fix for this incident. Apr 27, 07:31:57 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 27, 08:53:20 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 22 minutes Affected Components: Washington, D.C. - WAS Apr 23, 16:03:00 GMT+0 - Identified - One host in Washington region lost connectivity. As a result, Instances running on this machine were rescheduled to other hosts. Apr 23, 16:25:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 4 hours and 20 minutes Affected Components: Washington, D.C. - WAS Apr 6, 13:30:00 GMT+0 - Identified - We are working on a fix for this incident. Apr 6, 17:46:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 6, 17:50:17 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 15 hours and 58 minutes Affected Components: Frankfurt - FRA, Tokyo - TYO, Control Panel, San Francisco - SFO, Build / Provisioning, API, Third Party: Quay → Registry, Singapore - SIN, Washington, D.C. - WAS, Paris - PAR Mar 25, 07:08:22 GMT+0 - Investigating - We are currently investigating this incident. Mar 25, 07:48:19 GMT+0 - Resolved - This incident has been r…
Type: Incident Duration: 43 minutes Affected Components: San Francisco - SFO, , Washington, D.C. - WAS, North America → Mar 23, 14:41:42 GMT+0 - Investigating - We are currently investigating this incident. Mar 23, 15:13:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 23, 15:24:13 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 2 hours and 49 minutes Affected Components: Build / Provisioning Mar 21, 18:19:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 20, 19:00:00 GMT+0 - Investigating - We are currently investigating this incident. Mar 21, 13:49:00 GMT+0 - Resolved - This incident has been resolved. Mar 21, 21:49:00 GMT+0 - Resolved - This incident has b…
Type: Incident Duration: 59 minutes Affected Components: Build / Provisioning Mar 14, 10:27:39 GMT+0 - Investigating - We are currently investigating this incident. Mar 14, 11:26:53 GMT+0 - Resolved - This incident has been resolved.