Koyeb had 35 outages in the last 2 years totaling 46h 8m of downtime — averaging 1.4 incidents per month.
There were 35 Koyeb outages since October 7, 2025 totaling 46h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are currently investigating this incident.
We are currently investigating this incident. Other regions are healthy. As a workaround, redeploy to Frankfurt or any other region.
This incident has been resolved. Here the associated report from our provider for this region
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 this incident. EU region has been stabilized, NA is experiencing delays. Jun 16, 17:58:52 GMT+0 - Resolved - This incident has been resolved. 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.
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.
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.