Koyeb had 40 outages in the last 2 years totaling 56h 9m of downtime — averaging 1.6 incidents per month.
There were 40 Koyeb outages since October 7, 2025 totaling 56h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
This incident has been resolved.
Customers located in Asia are reporting an elevated rate of 404 when contacting their service.
This incident has been resolved. A crash on the load balancer stack caused some network propagation issue.
We are currently investigating this incident.
This incident has been resolved.
We are investigating this issue. Existing deployments are working not affected.
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 new custom domains or refreshed custom domains would be stuck in Pending. Jul 21, 11:29:00 GMT+0 - Resolved - This incident has been resolved.
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.
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.
This incident has been resolved.
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
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: 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.