Koyeb had 32 outages in the last 2 years totaling 49h 51m of downtime — averaging 1.3 incidents per month.
There were 32 Koyeb outages since October 7, 2025 totaling 49h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
Related status
This incident has been resolved.
We have identified an outage with our database provider. Database operations might fail in the mean time.
This incident has been resolved.
We are investigating the possible loss of an hypervisor node. We will update you as soon as we have more information.
This incident has been resolved.
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.
This incident has been resolved.
We are currently investigating this incident.
We are continuing to work on a fix for this incident.
Most regions are back to normal, but Tokyo is still lagging behind. We are still working on a fix for Tokyo region
We implemented a fix in Tokyo and are currently monitoring the result.
We are happy with the fix. Tokyo may still have a some delay but will be promptly resolved as well.
We are currently investigating this incident.
We are continuing to work on a fix for this incident.
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 SIN and TYO.
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.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
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.
One host in Washington region lost connectivity. As a result, Instances running on this machine were rescheduled to other hosts.
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: 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: 58 minutes Affected Components: Frankfurt - FRA, , Paris - PAR, Europe → Feb 25, 12:23:00 GMT+0 - Resolved - This incident has been resolved. Feb 25, 11:52:00 GMT+0 - Investigating -
Type: Incident Duration: 3 hours and 8 minutes Affected Components: Build / Provisioning Feb 19, 08:25:11 GMT+0 - Investigating - We are currently investigating deployment delay impacting all regions. Feb 19, 11:33:20 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 10 minutes Affected Components: San Francisco - SFO, Washington, D.C. - WAS Feb 16, 16:49:23 GMT+0 - Investigating - We are currently investigating this incident. Feb 16, 17:58:57 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 17 minutes Affected Components: Build / Provisioning Feb 10, 12:19:12 GMT+0 - Investigating - We are currently investigating this incident. Feb 10, 12:36:15 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 10 minutes Affected Components: Build / Provisioning, Third Party: Github → API Requests, Third Party: Github → Webhooks Feb 9, 19:59:51 GMT+0 - Identified - Features using GitHub might be affected due to a Github outage. Feb 9, 20:09:55 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 21 hours and 45 minutes Affected Components: Frankfurt - FRA, , Paris - PAR, Europe → Feb 9, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 9, 13:00:00 GMT+0 - Identified - Maintenance has completed successfully Feb 9, 22:45:07 GMT+0 - Completed - Maintenance has completed successfully. 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**.
Type: Incident Duration: 8 minutes Affected Components: Frankfurt - FRA Feb 4, 16:37:21 GMT+0 - Investigating - We are currently investigating this incident. Hypervisor id d82f4e74-c9ac-b2f5-74b6-81c087dc1da8 Feb 4, 16:43:59 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 4, 16:45:44 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 38 minutes Feb 1, 19:45:51 GMT+0 - Investigating - Feb 1, 20:15:00 GMT+0 - Monitoring - We are currently investigating the issue. Some services are back. Expect delays in provisioning new deployments. Feb 1, 21:23:51 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 53 minutes Affected Components: Singapore - SIN Jan 29, 09:19:00 GMT+0 - Identified - We are aware of an issue disturbing network on some hosts in Singapore region. If you encounter packet drops, consider: \- Deploying on another region \- or Redeploying on Singapore, new workload will be scheduled on sane machines Jan 29, 11:08:07 GMT+0 - Monitoring - We are seeing improvements with network stability Jan 29, 11:12:25 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 15 minutes Affected Components: Control Panel, API Jan 7, 11:15:00 GMT+0 - Investigating - We are currently investigating this incident. Jan 7, 11:30:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 5 hours and 40 minutes Affected Components: API Dec 20, 16:03:30 GMT+0 - Investigating - We are receiving reports from people having issues under certain conditions to access their database and access. Dec 20, 20:21:16 GMT+0 - Identified - We are continuing to work on a fix for this incident. We are restoring all paused databases. We identified that some databases had their password changed and some data were missing, and access to some databases were missing. We are progressively restoring access to all of them. We believe we have found the root cause of this issue, and we will provide more details later. Dec 20, 21:43:59 GMT+0 - Resolved - This incident has been resolved. The missing databases should now be recovered. A small portion of user have had their password changed due to the incident. They can log in to the control panel and retrieve it. Reach out to the support if you have issues or questions.