Duration: 29 minutes

Affected Components:

Sep 29, 13:45:00 GMT+0
Resolved - The provider had a networking issue that was resolved. The capacity is now back to normal..

Sep 29, 13:16:01 GMT+0
Identified - Due to an incident with a provider, we are short on capacity on was1. We are trying to restore capacity there. In the meantime, deployments in that region could be slow to be deployed. We suggest using other regions for the time being..

Duration: 52 minutes

Affected Components:

Sep 29, 09:37:57 GMT+0
Resolved - This incident has been resolved..

Sep 29, 08:46:26 GMT+0
Monitoring - _Some customers might be unable to provision new services due to an issue with quota enforcement_.

Duration: 45 minutes

Affected Components:

Sep 23, 16:38:18 GMT+0
Resolved - This incident has been resolved..

Sep 23, 16:24:34 GMT+0
Monitoring - We have pushed a fix and are monitoring, but things should be back to normal..

Sep 23, 15:53:24 GMT+0
Investigating - We are currently investigating this incident..

Duration: 13 minutes

Affected Components:

Sep 22, 15:17:32 GMT+0
Resolved - We implemented a fix and are currently monitoring the result..

Sep 22, 15:05:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Duration: 6 minutes

Affected Components: ,

Sep 21, 14:22:00 GMT+0
Resolved - This incident has been resolved..

Sep 21, 14:16:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Duration: 6 hours and 7 minutes

Affected Components:

Sep 15, 10:22:00 GMT+0
Resolved - This incident has been resolved..

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

Duration: 5 hours

Affected Components:

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

Sep 11, 02:00:00 GMT+0
Investigating - Customers located in Asia are reporting an elevated rate of 404 when contacting their service..

Duration: 20 minutes

Affected Components:

Sep 8, 07:25:00 GMT+0
Resolved - This incident has been resolved..

Sep 8, 07:05:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 minutes

Affected Components: ,

Jul 23, 15:17:51 GMT+0
Resolved - This incident has been resolved..

Jul 23, 15:16:00 GMT+0
Investigating - We are investigating this issue. Existing deployments are working not affected..

Duration: 1 hour and 59 minutes

Affected Components: , , , ,

Jul 21, 11:29:00 GMT+0
Resolved - This incident has been resolved..

Jul 21, 09:30:00 GMT+0
Investigating - We had an issue where new custom domains or refreshed custom domains would be stuck in Pending..

Duration: 5 hours and 30 minutes

Affected Components:

Jul 21, 04:00:00 GMT+0
Resolved - This incident has been resolved..

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.

Duration: 1 hour and 33 minutes

Affected Components:

Jul 16, 10:32:54 GMT+0
Resolved - This incident has been resolved..

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

Duration: 27 minutes

Affected Components:

Jun 27, 01:44:40 GMT+0
Resolved - This incident has been resolved..

Jun 26, 23:00:00 GMT+0
Investigating - .

Duration: 11 minutes

Affected Components: ,

Jun 23, 14:19:14 GMT+0
Resolved - This incident has been resolved..

Jun 23, 14:13:45 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jun 23, 14:08:37 GMT+0
Investigating - We are currently investigating this incident..

Duration: 29 minutes

Affected Components:

Jun 22, 09:34:53 GMT+0
Resolved - This incident has been resolved. Here the associated report from our provider for this region <https://status.scaleway.com/incidents/ycmhbnwwq005> .

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:05:46 GMT+0
Investigating - We are currently investigating this incident..

Duration: 6 hours and 9 minutes

Affected Components: , , ,

Jun 16, 17:58:52 GMT+0
Resolved - This incident has been resolved..

Jun 16, 15:34:17 GMT+0
Identified - We are continuing to work on a fix for this incident. EU region has been stabilized, NA is experiencing delays..

Jun 16, 14:57:32 GMT+0
Identified - We are continuing to work on a fix for this incident. The NA regions are affected too..

Jun 16, 12:22:23 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jun 16, 11:50:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 3 hours and 9 minutes

Jun 15, 11:34:22 GMT+0
Resolved - This incident has been resolved..

Jun 15, 10:12:07 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jun 15, 09:53:59 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jun 15, 08:25:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 day, 2 hours and 7 minutes

Affected Components:

Jun 5, 18:38:17 GMT+0
Resolved - This incident has been resolved..

Jun 5, 18:12:10 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 2 minutes

Affected Components:

Jun 1, 16:27:34 GMT+0
Resolved - This incident has been resolved..

Jun 1, 14:26:01 GMT+0
Identified - Related status <https://www.cloudflarestatus.com/incidents/59gsh0xrh6gg>.

Duration: 48 minutes

Affected Components:

Jun 1, 12:19:26 GMT+0
Resolved - This incident has been resolved..

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

Duration: 18 hours and 24 minutes

Affected Components:

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

Duration: 21 hours and 22 minutes

Affected Components:

May 26, 10:25:41 GMT+0
Resolved - This incident has been resolved..

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

Duration: 4 hours and 23 minutes

Affected Components:

May 15, 02:55:07 GMT+0
Resolved - We are happy with the fix. Tokyo may still have a some delay but will be promptly resolved as well..

May 15, 02:40:20 GMT+0
Monitoring - We implemented a fix in Tokyo and are currently monitoring the result..

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 fix for Tokyo region.

May 14, 22:50:59 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 14, 22:32:18 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 2 minutes

Affected Components:

May 11, 15:43:43 GMT+0
Resolved - This incident has been resolved..

May 11, 14:12:37 GMT+0
Identified - We are continuing to work on a fix for this incident..

May 11, 13:41:59 GMT+0
Investigating - We are currently investigating this incident..

Duration: 15 minutes

Affected Components: ,

May 5, 16:35:00 GMT+0
Resolved - This incident has been resolved..

May 5, 16:20:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 21 hours and 45 minutes

Affected Components: , ,

Feb 9, 22:45:07 GMT+0
Completed - Maintenance has completed successfully..

Feb 9, 13:00:00 GMT+0
Identified - Maintenance has completed successfully.

Feb 9, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 9, 01:00:00 GMT+0
Identified - We are performing an infrastructure maintenance to migrate storage to new machines. The maintenance will only impact hypervisor id e9c4cf8c-4f47-14d6-1ab0-6be5e88b6eb6 It will occur on **2026, Monday the 9th**, will take approximately half a day, and may causeup to **5 minutes of downtime per volume**..

Duration: 30 minutes

Affected Components: , ,

Oct 7, 19:30:00 GMT+0
Completed - Maintenance is now in progress.

Oct 7, 19:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 7, 19:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. We will be performing some network operations..

Duration: 1 day, 3 hours and 22 minutes

Affected Components:

Mar 11, 14:17:09 GMT+0
Completed - Maintenance has completed successfully..

Mar 10, 10:57:10 GMT+0
Identified - Maintenance is now in progress..

Mar 10, 10:55:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. There should be no downtime during that time.

Affected Components:

Feb 14, 10:05:25 GMT+0
Completed - We will migrate apps and services located in San Francisco to a new datacenter we deployed in this region. The migration will automatically trigger a redeployment of services with no downtime. There is no action required from your end..

Duration: 3 hours and 39 minutes

Affected Components:

Oct 7, 14:14:22 GMT+0
Completed - Maintenance has completed successfully..

Oct 7, 10:35:01 GMT+0
Identified - Maintenance is now in progress.

Oct 7, 10:35:00 GMT+0
Identified - We will migrate apps and services to our [**new network stack**](https://link.koyeb.com/e/c/eyJlbWFpbF9pZCI6ImRnVHUtd2NEQUpmUkFaYlJBUUdTS1ZjRVhLaFJ4UXFzd0NOcERSUT0iLCJocmVmIjoiaHR0cHM6Ly9jb21tdW5pdHkua295ZWIuY29tL3Qvcm9sbGluZy1vdXQtb3VyLW5ldy1uZXR3b3JraW5nLXN0YWNrLWZvci0zeC1mYXN0ZXItZGVwbG95bWVudHMvMjE1Nj91dG1fY2FtcGFpZ249MjAyNDA5MjQtZmluYWwta2F0YS1taWdyYXRpb25cdTAwMjZ1dG1fY29udGVudD0yMDI0MDkyNC1maW5hbC1rYXRhLW1pZ3JhdGlvblx1MDAyNnV0bV9tZWRpdW09ZW1haWxfYWN0aW9uXHUwMDI2dXRtX3NvdXJjZT1rbWFpbCIsImludGVybmFsIjoiZWVmYjA3MDA5NmQxMDE5N2QxMDEiLCJsaW5rX2lkIjoxNDcyfQ/c7003a9e56406757be500fb10641dece09214a3476a29164706d96764ef63c97) in Frankfurt. If this migration affects you, you should have received an email on September 25th. The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most..

Duration: 3 hours and 54 minutes

Affected Components:

Oct 7, 12:47:25 GMT+0
Completed - Maintenance has completed successfully..

Oct 7, 08:53:01 GMT+0
Identified - Maintenance is now in progress.

Oct 7, 08:53:00 GMT+0
Identified - We will migrate apps and services to our [**new network stack**](https://link.koyeb.com/e/c/eyJlbWFpbF9pZCI6ImRnVHUtd2NEQUpmUkFaYlJBUUdTS1ZjRVhLaFJ4UXFzd0NOcERSUT0iLCJocmVmIjoiaHR0cHM6Ly9jb21tdW5pdHkua295ZWIuY29tL3Qvcm9sbGluZy1vdXQtb3VyLW5ldy1uZXR3b3JraW5nLXN0YWNrLWZvci0zeC1mYXN0ZXItZGVwbG95bWVudHMvMjE1Nj91dG1fY2FtcGFpZ249MjAyNDA5MjQtZmluYWwta2F0YS1taWdyYXRpb25cdTAwMjZ1dG1fY29udGVudD0yMDI0MDkyNC1maW5hbC1rYXRhLW1pZ3JhdGlvblx1MDAyNnV0bV9tZWRpdW09ZW1haWxfYWN0aW9uXHUwMDI2dXRtX3NvdXJjZT1rbWFpbCIsImludGVybmFsIjoiZWVmYjA3MDA5NmQxMDE5N2QxMDEiLCJsaW5rX2lkIjoxNDcyfQ/c7003a9e56406757be500fb10641dece09214a3476a29164706d96764ef63c97) in Washington. If this migration affects you, you should have received an email on September 25th. The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most..

Duration: 2 days, 11 hours and 1 minute

Affected Components:

Oct 4, 19:53:16 GMT+0
Completed - Maintenance has completed successfully..

Oct 2, 08:52:40 GMT+0
Identified - Maintenance is now in progress..

Oct 2, 08:51:56 GMT+0
Identified - We will migrate apps and services to our [**new network stack**](https://link.koyeb.com/e/c/eyJlbWFpbF9pZCI6ImRnVHUtd2NEQUpmUkFaYlJBUUdTS1ZjRVhLaFJ4UXFzd0NOcERSUT0iLCJocmVmIjoiaHR0cHM6Ly9jb21tdW5pdHkua295ZWIuY29tL3Qvcm9sbGluZy1vdXQtb3VyLW5ldy1uZXR3b3JraW5nLXN0YWNrLWZvci0zeC1mYXN0ZXItZGVwbG95bWVudHMvMjE1Nj91dG1fY2FtcGFpZ249MjAyNDA5MjQtZmluYWwta2F0YS1taWdyYXRpb25cdTAwMjZ1dG1fY29udGVudD0yMDI0MDkyNC1maW5hbC1rYXRhLW1pZ3JhdGlvblx1MDAyNnV0bV9tZWRpdW09ZW1haWxfYWN0aW9uXHUwMDI2dXRtX3NvdXJjZT1rbWFpbCIsImludGVybmFsIjoiZWVmYjA3MDA5NmQxMDE5N2QxMDEiLCJsaW5rX2lkIjoxNDcyfQ/c7003a9e56406757be500fb10641dece09214a3476a29164706d96764ef63c97) in Frankfurt. If this migration affects you, you should have received an email on September 25th. The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most..

Duration: 2 hours and 12 minutes

Affected Components:

Sep 26, 17:00:00 GMT+0
Completed - Maintenance has completed successfully..

Sep 26, 14:47:44 GMT+0
Identified - Maintenance is now in progress..

Sep 26, 14:45:06 GMT+0
Identified - We will migrate apps and services to our [**new network stack**](https://link.koyeb.com/e/c/eyJlbWFpbF9pZCI6ImRnVHUtd2NEQUpmUkFaYlJBUUdTS1ZjRVhLaFJ4UXFzd0NOcERSUT0iLCJocmVmIjoiaHR0cHM6Ly9jb21tdW5pdHkua295ZWIuY29tL3Qvcm9sbGluZy1vdXQtb3VyLW5ldy1uZXR3b3JraW5nLXN0YWNrLWZvci0zeC1mYXN0ZXItZGVwbG95bWVudHMvMjE1Nj91dG1fY2FtcGFpZ249MjAyNDA5MjQtZmluYWwta2F0YS1taWdyYXRpb25cdTAwMjZ1dG1fY29udGVudD0yMDI0MDkyNC1maW5hbC1rYXRhLW1pZ3JhdGlvblx1MDAyNnV0bV9tZWRpdW09ZW1haWxfYWN0aW9uXHUwMDI2dXRtX3NvdXJjZT1rbWFpbCIsImludGVybmFsIjoiZWVmYjA3MDA5NmQxMDE5N2QxMDEiLCJsaW5rX2lkIjoxNDcyfQ/c7003a9e56406757be500fb10641dece09214a3476a29164706d96764ef63c97) in Washington. If this migration affects you, you should have received an email on September 25th. The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most..

Duration: 3 hours and 10 minutes

Affected Components:

Sep 13, 20:25:01 GMT+0
Completed - Maintenance has completed successfully..

Sep 13, 17:14:43 GMT+0
Identified - Maintenance is now in progress..

Sep 13, 17:14:17 GMT+0
Identified - The migration will automatically trigger a redeployment of your services running in Tokyo with 60 seconds of connectivity loss at most..

Duration: 1 hour and 46 minutes

Affected Components:

Sep 13, 16:47:48 GMT+0
Completed - Maintenance has completed successfully..

Sep 13, 15:01:21 GMT+0
Identified - The migration will automatically trigger a redeployment of your services running in San Francisco with 60 seconds of connectivity loss at most..

Duration: 2 hours

Affected Components: ,

Oct 17, 10:00:00 GMT+0
Completed - Maintenance has completed successfully.

Oct 17, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 17, 08:00:00 GMT+0
Identified - We are planning a database update at 8:00 UTC. We might experience an increased rate of API call failure, the control panel might be unresponsive for a few minutes. Provisioning may be delayed for a few minutes. No impact on running services. .

Duration: 27 minutes

Affected Components:

Oct 6, 15:16:51 GMT+0
Completed - Maintenance has completed successfully..

Oct 6, 14:50:00 GMT+0
Identified - We will operate a maintenance of our logs backends. As a result, recent logs will not be delivered for the duration of the maintenance. No data loss is expected: those logs will be accessible after the maintenance is completed..

Duration: 1 hour

Affected Components: ,

May 2, 12:00:14 GMT+0
Completed - The maintenance is now completed..

May 2, 11:00:34 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

May 2, 10:00:01 GMT+0
Identified - Maintenance will begin as scheduled in 60 minutes..

Apr 28, 12:25:22 GMT+0
Identified - We will be updating part of our infrastructure. There should be some minor disruption in our API (ex: 50X errors, timeouts). No disruption is planned for the services hosted in Koyeb..

Duration: 1 hour

Affected Components: ,

Dec 14, 14:31:43 GMT+0
Completed - Update went smoothly, everything is back to normal..

Dec 14, 14:00:42 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Dec 14, 13:00:28 GMT+0
Identified - Maintenance will begin as scheduled in 60 minutes..

Dec 14, 10:51:47 GMT+0
Identified - We will be updating part of our infrastructure. There should be some minor disruption in our API (ex: 50X errors, timeouts). No disruption is planned for the services hosted in Koyeb..

Duration: 30 minutes

Affected Components: ,

Nov 25, 17:15:24 GMT+0
Completed - The scheduled maintenance has been completed..

Nov 25, 16:45:41 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Nov 25, 16:18:15 GMT+0
Identified - We will be updating part of our infrastructure. There should be some minor disruption in our API (ex: 50X errors, timeouts). No disruption is planned for the services hosted in Koyeb..

Duration: 3 hours

Affected Components: ,

Oct 12, 17:55:45 GMT+0
Completed - The scheduled maintenance has been completed..

Oct 12, 17:54:32 GMT+0
Identified - Scheduled maintenance is still in progress. We will provide updates as necessary..

Oct 12, 15:00:40 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Oct 12, 14:00:52 GMT+0
Identified - Maintenance will begin as scheduled in 60 minutes..

Oct 12, 12:26:30 GMT+0
Identified - We are performing a maintenance on one of our core platform component. We might have some disruption on the API and provisioning of new service might be impacted for a few minutes..

Duration: 2 hours

Affected Components: ,

Sep 13, 11:01:20 GMT+0
Completed - The scheduled maintenance has been completed..

Sep 13, 10:17:27 GMT+0
Identified - Verification is currently underway for the maintenance items..

Sep 13, 09:00:33 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Sep 13, 08:00:23 GMT+0
Identified - Maintenance will begin as scheduled in 60 minutes..

Sep 9, 14:47:08 GMT+0
Identified - We will be updating part of our infrastructure. There should be some minor disruption in our API (ex: 50X errors, timeouts). No disruption is planned for the services hosted in Koyeb..

Duration: 2 hours

Affected Components:

Mar 16, 17:35:23 GMT+0
Completed - The scheduled maintenance has been completed..

Mar 16, 14:40:18 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Mar 16, 14:34:10 GMT+0
Identified - We will perform a network update to improve performances and provide new services such as websocket and custom domains (coming soon)..

Duration: 2 hours

Affected Components: ,

Mar 16, 12:30:23 GMT+0
Completed - The scheduled maintenance has been completed..

Mar 16, 09:28:24 GMT+0
Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary..

Mar 16, 09:28:00 GMT+0
Identified - We are performing a maintenance on one of our core platform component. Provisioning of new service might be impacted for a few minutes..