Koyeb Outage History

Koyeb is up right now

Koyeb had 45 outages in the last 2 years totaling 58h 22m of downtime — averaging 1.8 incidents per month.

There were 45 Koyeb outages since October 7, 2025 totaling 58h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.koyeb.com

Minor September 29, 2026

Low availabilty on was1

Detected by Pingoru
Sep 29, 2026, 01:16 PM UTC
Resolved
Sep 29, 2026, 01:45 PM UTC
Duration
28m
Affected: North America (Washington, D.C. - WAS)
Timeline · 2 updates
  1. identified Sep 29, 2026, 01:16 PM UTC

    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.

  2. resolved Sep 29, 2026, 01:45 PM UTC

    The provider had a networking issue that was resolved. The capacity is now back to normal.

Read the full incident report →

Minor September 29, 2026

Provisioning error for new services

Detected by Pingoru
Sep 29, 2026, 08:46 AM UTC
Resolved
Sep 29, 2026, 09:37 AM UTC
Duration
51m
Affected: API
Timeline · 2 updates
  1. monitoring Sep 29, 2026, 08:46 AM UTC

    Quotas for accounts are not properly honored. We deployed a mitigation and are continuing to monitor the situation.

  2. resolved Sep 29, 2026, 09:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 23, 2026

API timing out

Detected by Pingoru
Sep 23, 2026, 03:53 PM UTC
Resolved
Sep 23, 2026, 04:38 PM UTC
Duration
44m
Affected: API
Timeline · 3 updates
  1. investigating Sep 23, 2026, 03:53 PM UTC

    We are currently investigating this incident.

  2. monitoring Sep 23, 2026, 04:24 PM UTC

    We have pushed a fix and are monitoring, but things should be back to normal.

  3. resolved Sep 23, 2026, 04:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 22, 2026

Authentication issue

Detected by Pingoru
Sep 22, 2026, 03:05 PM UTC
Resolved
Sep 22, 2026, 03:17 PM UTC
Duration
12m
Affected: API
Timeline · 2 updates
  1. identified Sep 22, 2026, 03:05 PM UTC

    We are continuing to work on a fix for this incident.

  2. resolved Sep 22, 2026, 03:17 PM UTC

    We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor September 22, 2026

Builds in pending in FRA

Detected by Pingoru
Sep 22, 2026, 07:49 AM UTC
Resolved
Sep 22, 2026, 08:06 AM UTC
Duration
16m
Affected: Build / Provisioning
Timeline · 1 update
  1. identified Sep 22, 2026, 07:49 AM UTC

    We are continuing to work on a fix for this incident.

Read the full incident report →

Minor September 15, 2026

RTXA6000 currently unavailable

Detected by Pingoru
Sep 15, 2026, 07:16 AM UTC
Resolved
Sep 15, 2026, 10:22 AM UTC
Duration
3h 5m
Affected: North America (Washington, D.C. - WAS)
Timeline · 2 updates
  1. identified Sep 15, 2026, 07:16 AM UTC

    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.

  2. resolved Sep 15, 2026, 10:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 11, 2026

Singapore load balancing issue

Detected by Pingoru
Sep 11, 2026, 02:00 AM UTC
Resolved
Sep 11, 2026, 07:00 AM UTC
Duration
5h
Affected: Asia–Pacific - APAC (Singapore - SIN)
Timeline · 2 updates
  1. investigating Sep 11, 2026, 02:00 AM UTC

    Customers located in Asia are reporting an elevated rate of 404 when contacting their service.

  2. resolved Sep 11, 2026, 07:00 AM UTC

    This incident has been resolved. A crash on the load balancer stack caused some network propagation issue.

Read the full incident report →

Minor September 8, 2026

Deployment delay

Detected by Pingoru
Sep 08, 2026, 07:05 AM UTC
Resolved
Sep 08, 2026, 07:25 AM UTC
Duration
20m
Affected: Build / Provisioning
Timeline · 2 updates
  1. investigating Sep 08, 2026, 07:05 AM UTC

    We are currently investigating this incident.

  2. resolved Sep 08, 2026, 07:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 23, 2026

500s on APIs

Detected by Pingoru
Jul 23, 2026, 03:16 PM UTC
Resolved
Jul 23, 2026, 03:17 PM UTC
Duration
1m
Affected: Control PanelAPI
Timeline · 2 updates
  1. investigating Jul 23, 2026, 03:16 PM UTC

    We are investigating this issue. Existing deployments are working not affected.

  2. resolved Jul 23, 2026, 03:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 21, 2026

Reconciliation delays for custom domains

Detected by Pingoru
Jul 21, 2026, 09:30 AM UTC
Resolved
Jul 21, 2026, 09:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 21, 2026, 09:30 AM UTC

    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.

Read the full incident report →

Minor July 20, 2026

Provisioning delays

Detected by Pingoru
Jul 20, 2026, 10:30 PM UTC
Resolved
Jul 20, 2026, 10:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 20, 2026, 10:30 PM UTC

    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.

Read the full incident report →

Major July 16, 2026

Login failure

Detected by Pingoru
Jul 16, 2026, 08:59 AM UTC
Resolved
Jul 16, 2026, 10:32 AM UTC
Duration
1h 33m
Affected: Control Panel
Timeline · 2 updates
  1. identified Jul 16, 2026, 08:59 AM UTC

    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.

  2. resolved Jul 16, 2026, 10:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2026

Disruption for new deployments

Detected by Pingoru
Jun 26, 2026, 11:00 PM UTC
Resolved
Jun 26, 2026, 11:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 26, 2026, 11:00 PM UTC

    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.

Read the full incident report →

Major June 23, 2026

Scheduling issue in EU region

Detected by Pingoru
Jun 23, 2026, 02:08 PM UTC
Resolved
Jun 23, 2026, 02:19 PM UTC
Duration
10m
Affected: Europe (Frankfurt - FRA)Europe (Paris - PAR)
Timeline · 3 updates
  1. investigating Jun 23, 2026, 02:08 PM UTC

    We are currently investigating this incident.

  2. monitoring Jun 23, 2026, 02:13 PM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Jun 23, 2026, 02:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 22, 2026

Connectivity issues in PAR

Detected by Pingoru
Jun 22, 2026, 09:05 AM UTC
Resolved
Jun 22, 2026, 09:34 AM UTC
Duration
29m
Affected: Europe (Paris - PAR)
Timeline · 3 updates
  1. investigating Jun 22, 2026, 09:05 AM UTC

    We are currently investigating this incident.

  2. investigating Jun 22, 2026, 09:16 AM UTC

    We are currently investigating this incident. Other regions are healthy. As a workaround, redeploy to Frankfurt or any other region.

  3. resolved Jun 22, 2026, 09:34 AM UTC

    This incident has been resolved. Here the associated report from our provider for this region

Read the full incident report →

Notice June 5, 2026

Provisioning delays in APAC region

Detected by Pingoru
Jun 05, 2026, 06:12 PM UTC
Resolved
Jun 05, 2026, 06:38 PM UTC
Duration
26m
Affected: Build / Provisioning
Timeline · 2 updates
  1. investigating Jun 05, 2026, 06:12 PM UTC

    We are currently investigating this incident.

  2. monitoring Jun 05, 2026, 06:38 PM UTC

    We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor June 1, 2026

Custom domain provisioning delay

Detected by Pingoru
Jun 01, 2026, 02:26 PM UTC
Resolved
Jun 01, 2026, 04:27 PM UTC
Duration
2h 1m
Affected: Build / Provisioning
Timeline · 2 updates
  1. identified Jun 01, 2026, 02:26 PM UTC

    Related status

  2. resolved Jun 01, 2026, 04:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 1, 2026

Databases operations failures

Detected by Pingoru
Jun 01, 2026, 11:31 AM UTC
Resolved
Jun 01, 2026, 12:19 PM UTC
Duration
47m
Affected: Build / Provisioning
Timeline · 2 updates
  1. identified Jun 01, 2026, 11:31 AM UTC

    We have identified an outage with our database provider. Database operations might fail in the mean time.

  2. resolved Jun 01, 2026, 12:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 26, 2026

Hypervisor unreachable

Detected by Pingoru
May 26, 2026, 06:47 PM UTC
Resolved
May 27, 2026, 01:11 PM UTC
Duration
18h 24m
Affected: Europe (Frankfurt - FRA)
Timeline · 2 updates
  1. investigating May 26, 2026, 06:47 PM UTC

    We are investigating the possible loss of an hypervisor node. We will update you as soon as we have more information.

  2. resolved May 27, 2026, 01:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 25, 2026

Hypervisor unavailable

Detected by Pingoru
May 25, 2026, 01:04 PM UTC
Resolved
May 26, 2026, 10:25 AM UTC
Duration
21h 21m
Affected: Europe (Frankfurt - FRA)
Timeline · 2 updates
  1. identified May 25, 2026, 01:04 PM UTC

    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.

  2. resolved May 26, 2026, 10:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026

Provisioning delay

Detected by Pingoru
May 11, 2026, 01:41 PM UTC
Resolved
May 11, 2026, 03:43 PM UTC
Duration
2h 1m
Affected: Build / Provisioning
Timeline · 3 updates
  1. investigating May 11, 2026, 01:41 PM UTC

    We are currently investigating this incident.

  2. identified May 11, 2026, 02:12 PM UTC

    We are continuing to work on a fix for this incident.

  3. resolved May 11, 2026, 03:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026

Provisioning delay and wake up delay in SIN

Detected by Pingoru
May 04, 2026, 06:30 AM UTC
Resolved
May 04, 2026, 06:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 04, 2026, 06:30 AM UTC

    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.

Read the full incident report →

Minor May 3, 2026

Hypervisor lost

Detected by Pingoru
May 03, 2026, 04:30 PM UTC
Resolved
May 03, 2026, 04:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 03, 2026, 04:30 PM UTC

    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.

Read the full incident report →

Minor April 29, 2026

Provisionning delay

Detected by Pingoru
Apr 29, 2026, 11:46 AM UTC
Resolved
Apr 29, 2026, 11:50 AM UTC
Duration
4m
Affected: Build / Provisioning
Timeline · 3 updates
  1. investigating Apr 29, 2026, 11:46 AM UTC

    We are currently investigating this incident.

  2. monitoring Apr 29, 2026, 11:49 AM UTC

    We implemented a fix and are currently monitoring the result.

  3. resolved Apr 29, 2026, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 27, 2026

Delay provisioning and wake up

Detected by Pingoru
Apr 27, 2026, 07:30 AM UTC
Resolved
Apr 27, 2026, 07:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 27, 2026, 07:30 AM UTC

    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.

Read the full incident report →