Koyeb Status - Incident history https://status.koyeb.com Koyeb Sat, 14 Mar 2026 10:27:39 +0000 Provisioning delays Type: Incident Duration: 59 minutes Affected Components: Build / Provisioning Mar 14, 10:27:39 GMT+0 - Investigating - We are currently investigating this incident. Mar 14, 11:26:53 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 59 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>10:27:39</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 14</var>, <var data-var='time'>11:26:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 14 Mar 2026 10:27:39 +0000 https://status.koyeb.com/incident/cmmq6mab90772qd4ciwrp2zfi https://status.koyeb.com/incident/cmmq6mab90772qd4ciwrp2zfi Deployment delays in Europe 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: 58 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>12:23:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>11:52:00</var> GMT+0</small><br><strong>Investigating</strong> - .</p> ]]> Wed, 25 Feb 2026 11:52:00 +0000 https://status.koyeb.com/incident/cmm20755f0brav24kiapmxqv5 https://status.koyeb.com/incident/cmm20755f0brav24kiapmxqv5 Deployment delay 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: 3 hours and 8 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>08:25:11</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating deployment delay impacting all regions..</p> <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>11:33:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 19 Feb 2026 08:25:11 +0000 https://status.koyeb.com/incident/cmlt747o801pagoe2t4aog4hz https://status.koyeb.com/incident/cmlt747o801pagoe2t4aog4hz Provisioning delay in WAS / SFO 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: 1 hour and 10 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>16:49:23</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>17:58:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 16 Feb 2026 16:49:23 +0000 https://status.koyeb.com/incident/cmlpet1or0vb1u10wsdvodjfh https://status.koyeb.com/incident/cmlpet1or0vb1u10wsdvodjfh New deployments delays 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: 17 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>12:19:12</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>12:36:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 10 Feb 2026 12:19:12 +0000 https://status.koyeb.com/incident/cmlgkihnq14r661ojiwa7qtd8 https://status.koyeb.com/incident/cmlgkihnq14r661ojiwa7qtd8 GitHub deployments degraded 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. <https://www.githubstatus.com/incidents/lcw3tg2f6zsd> Feb 9, 20:09:55 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 10 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>19:59:51</var> GMT+0</small><br><strong>Identified</strong> - Features using GitHub might be affected due to a Github outage. <https://www.githubstatus.com/incidents/lcw3tg2f6zsd>.</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>20:09:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 9 Feb 2026 19:59:51 +0000 https://status.koyeb.com/incident/cmlflj1ct00ass8r1pw7faqyr https://status.koyeb.com/incident/cmlflj1ct00ass8r1pw7faqyr Volume Migration - Infrastructure Upgrade 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: Maintenance

Duration: 21 hours and 45 minutes

Affected Components: , ,

<p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - Maintenance has completed successfully.</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>22:45:07</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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**..</p> ]]> Mon, 9 Feb 2026 01:00:00 +0000 https://status.koyeb.com/maintenance/cml9orzgw01au5wvkr6dnbpf8 https://status.koyeb.com/maintenance/cml9orzgw01au5wvkr6dnbpf8 Hypervisor network failure 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: 8 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:37:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Hypervisor id d82f4e74-c9ac-b2f5-74b6-81c087dc1da8.</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:43:59</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Feb <var data-var='date'> 4</var>, <var data-var='time'>16:45:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 4 Feb 2026 16:37:21 +0000 https://status.koyeb.com/incident/cml893d18000htp3zer0n9a47 https://status.koyeb.com/incident/cml893d18000htp3zer0n9a47 Downtime in Washington and San Francisco 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 38 minutes

<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>19:45:51</var> GMT+0</small><br><strong>Investigating</strong> - .</p> <p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>20:15:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently investigating the issue. Some services are back. Expect delays in provisioning new deployments. .</p> <p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>21:23:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 1 Feb 2026 19:45:51 +0000 https://status.koyeb.com/incident/cml45i83t01abo6w8w0lr0soa https://status.koyeb.com/incident/cml45i83t01abo6w8w0lr0soa Disturbed network 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 53 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>09:19:00</var> GMT+0</small><br><strong>Identified</strong> - 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.</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>11:08:07</var> GMT+0</small><br><strong>Monitoring</strong> - We are seeing improvements with network stability.</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>11:12:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 29 Jan 2026 09:19:00 +0000 https://status.koyeb.com/incident/cmkzbac7x0ykrytjohldd8hni https://status.koyeb.com/incident/cmkzbac7x0ykrytjohldd8hni Provisioning delays Type: Incident Duration: 30 minutes Affected Components: Build / Provisioning Jan 12, 20:53:29 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 12, 20:58:15 GMT+0 - Resolved - This incident has been resolved. Jan 12, 20:27:57 GMT+0 - Investigating - We are aware of new deployments being stuck provisioning. Type: Incident

Duration: 30 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>20:53:29</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>20:58:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>20:27:57</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of new deployments being stuck provisioning..</p> ]]> Mon, 12 Jan 2026 20:27:57 +0000 https://status.koyeb.com/incident/cmkbm7b7b005svoa3zyusaz7e https://status.koyeb.com/incident/cmkbm7b7b005svoa3zyusaz7e Elevated rate of 500 error causing unavailability 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: 1 hour and 15 minutes

Affected Components: ,

<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>11:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 7 Jan 2026 11:15:00 +0000 https://status.koyeb.com/incident/cmk3y2ikl00bsosppi4z2b7qe https://status.koyeb.com/incident/cmk3y2ikl00bsosppi4z2b7qe Database access issue 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. Type: Incident

Duration: 5 hours and 40 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>16:03:30</var> GMT+0</small><br><strong>Investigating</strong> - We are receiving reports from people having issues under certain conditions to access their database and access..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>20:21:16</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>21:43:59</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Sat, 20 Dec 2025 16:03:30 +0000 https://status.koyeb.com/incident/cmjehmnko03wf11dqezdl8yzl https://status.koyeb.com/incident/cmjehmnko03wf11dqezdl8yzl Some services are currently unavailable Type: Incident Duration: 3 hours and 56 minutes Affected Components: Frankfurt - FRA, Tokyo - TYO, , , Singapore - SIN, San Francisco - SFO, Washington, D.C. - WAS, , Paris - PAR, North America → Europe → Asia–Pacific - APAC → Dec 22, 20:51:34 GMT+0 - Postmortem - # **Incident Summary** On November 20, 2025 at 12:00 UTC, we experienced a service disruption that impacted workloads running on Koyeb. During this incident, affected services were inaccessible between 20 minutes and 3 hours 30 for hobbyist workload. The incident was triggered by a human error that altered one of our system databases and unintentionally paused a large number of services. # **What happened** A change intended for an internal environment was mistakenly applied to production, causing nearly all production services to transition into a paused state. Pausing a service is an action we expose to Koyeb users to temporarily suspend a service. When a service is paused, its configuration is preserved, it can be resumed at any time, and no charges are incurred while it remains paused. This state is typically used intentionally by users, not as part of platform operations. At Koyeb, most of the resources follow a defined lifecycle and are continuously reconciled to match their desired state. This reconciliation loop is responsible for ensuring services converge toward the expected configuration. This incident began when an unintended change set the desired state of many services to **_paused_**. When the reconciliation loop ran, it applied that state and began pausing the affected services. Immediately after identifying the issue, we reverted the change. About 15 minutes after the incident began, services started to recover in three ways: 1. Users could resume their services themselves and recover immediately. 2. We intervened and prioritized restoring critical customers workloads ourselves. 3. In parallel, we worked to gradually recover the remaining services as fast as possible. Approximately 30 minutes after the incident began, critical and business customer workloads were back online. About 1 hour 50 minutes after the incident, additional recovery steps were applied to allow the remaining affected services to fully recover. ## **Impact on Postgres services** During recovery, we uncovered a secondary issue affecting a small subset of users. A bug in our database recovery logic caused database roles to be re-provisioned while services were transitioning through paused and resuming states. As a result, database user passwords for affected Postgres services were changed, making existing credentials invalid. Because we don’t store database passwords, the original credentials couldn’t be restored. We directly supported affected users and sent targeted communications with instructions to update their configuration. # **Incident Timeline** * **2025-12-20 12:00** \- A faulty manual operation was executed during an internal change. * **2025-12-20 12:00** \- Services began transitioning into a _pausing_ state. Traffic to affected services started returning HTTP 404. * **2025-12-20 12:15** \- The rate of 404 started to raise significantly as our systems moved more services to the _Paused_ state. * **2025-12-20 12:29** \- Impact reached its peak. At that point, the majority of Instances on the platform were stopped. * **2025-12-20 12:30** \- We started to recover Services, giving priority to critical and business customer workloads. * **2025-12-20 12:46** \- The majority of business workload had recovered. * **2025-12-20 13:31** \- While manually restoring critical workloads, we worked on a mechanism to enable batch restores while skipping builds, allowing faster recovery for affected services. * **2025-12-20 14:10** \- We started to batch recover all remaining services. * **2025-12-20 14:25** \- By then, more than 50% of remaining services had recovered. * **2025-12-20 16:00** \- All services were fully recovered. ## **Corrective and Preventative Measures** We’re already changing the system and our processes to prevent this kind of outage from occurring again. Below are the first measures we’re taking; some already implemented, while others are in progress: * **Rate limiting for reconciliations:** a mechanism to throttle reconciliations. It will ensure mass operations happen over a long period of time, giving us time to react and revert changes in case of unexpected changes. * **Audited database services recovery paths**: recovery logic has been reviewed and fixed to prevent unintended service state changes. * **Mandatory approval by a peer for a set of admin operations,** including batch changes. On-call engineers can escalate incidents to a peer to get an approval during off-hours. * **More robust service state evaluation:** simplified state handling by focusing on the intended service state rather than individual intermediate transitions, reducing the risk of unexpected or unhandled state changes. # **Conclusion** This incident should not have happened and the impact is totally unacceptable. We should not have been able to affect production at this scale, and our existing safeguards failed to contain the incident. We take full responsibility for this failure. The root cause was not an individual action, but gaps in our systems, tooling, and processes that allowed a small error to escalate into a broad outage. We are already acting on multiple fronts to prevent any forms of recurrence, with some corrective measures already in place and others actively in progress (see above). These changes are focused on preventing similar mistakes from reaching production, limiting how far mistakes can propagate and improving recovery behavior to be safer and more predictable. As always, feel free to contact us in case you need anything. We’re committed to doing better. Dec 20, 12:10:35 GMT+0 - Investigating - We are currently investigating this incident. Dec 20, 13:13:44 GMT+0 - Identified - We are working on a fix, you may resume your services to recover your service faster. We are continuing to work on a fix for this incident. Dec 20, 14:47:12 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. The majority of the services have been recovered; we are still recovering some of the free services. Dec 20, 16:06:43 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 56 minutes

Affected Components: , , , , , , , ,

<p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>20:51:34</var> GMT+0</small><br><strong>Postmortem</strong> - # **Incident Summary** On November 20, 2025 at 12:00 UTC, we experienced a service disruption that impacted workloads running on Koyeb. During this incident, affected services were inaccessible between 20 minutes and 3 hours 30 for hobbyist workload. The incident was triggered by a human error that altered one of our system databases and unintentionally paused a large number of services. # **What happened** A change intended for an internal environment was mistakenly applied to production, causing nearly all production services to transition into a paused state. Pausing a service is an action we expose to Koyeb users to temporarily suspend a service. When a service is paused, its configuration is preserved, it can be resumed at any time, and no charges are incurred while it remains paused. This state is typically used intentionally by users, not as part of platform operations. At Koyeb, most of the resources follow a defined lifecycle and are continuously reconciled to match their desired state. This reconciliation loop is responsible for ensuring services converge toward the expected configuration. This incident began when an unintended change set the desired state of many services to **_paused_**. When the reconciliation loop ran, it applied that state and began pausing the affected services. Immediately after identifying the issue, we reverted the change. About 15 minutes after the incident began, services started to recover in three ways: 1. Users could resume their services themselves and recover immediately. 2. We intervened and prioritized restoring critical customers workloads ourselves. 3. In parallel, we worked to gradually recover the remaining services as fast as possible. Approximately 30 minutes after the incident began, critical and business customer workloads were back online. About 1 hour 50 minutes after the incident, additional recovery steps were applied to allow the remaining affected services to fully recover. ## **Impact on Postgres services** During recovery, we uncovered a secondary issue affecting a small subset of users. A bug in our database recovery logic caused database roles to be re-provisioned while services were transitioning through paused and resuming states. As a result, database user passwords for affected Postgres services were changed, making existing credentials invalid. Because we don’t store database passwords, the original credentials couldn’t be restored. We directly supported affected users and sent targeted communications with instructions to update their configuration. # **Incident Timeline** * **2025-12-20 12:00** \- A faulty manual operation was executed during an internal change. * **2025-12-20 12:00** \- Services began transitioning into a _pausing_ state. Traffic to affected services started returning HTTP 404. * **2025-12-20 12:15** \- The rate of 404 started to raise significantly as our systems moved more services to the _Paused_ state. * **2025-12-20 12:29** \- Impact reached its peak. At that point, the majority of Instances on the platform were stopped. * **2025-12-20 12:30** \- We started to recover Services, giving priority to critical and business customer workloads. * **2025-12-20 12:46** \- The majority of business workload had recovered. * **2025-12-20 13:31** \- While manually restoring critical workloads, we worked on a mechanism to enable batch restores while skipping builds, allowing faster recovery for affected services. * **2025-12-20 14:10** \- We started to batch recover all remaining services. * **2025-12-20 14:25** \- By then, more than 50% of remaining services had recovered. * **2025-12-20 16:00** \- All services were fully recovered. ## **Corrective and Preventative Measures** We’re already changing the system and our processes to prevent this kind of outage from occurring again. Below are the first measures we’re taking; some already implemented, while others are in progress: * **Rate limiting for reconciliations:** a mechanism to throttle reconciliations. It will ensure mass operations happen over a long period of time, giving us time to react and revert changes in case of unexpected changes. * **Audited database services recovery paths**: recovery logic has been reviewed and fixed to prevent unintended service state changes. * **Mandatory approval by a peer for a set of admin operations,** including batch changes. On-call engineers can escalate incidents to a peer to get an approval during off-hours. * **More robust service state evaluation:** simplified state handling by focusing on the intended service state rather than individual intermediate transitions, reducing the risk of unexpected or unhandled state changes. # **Conclusion** This incident should not have happened and the impact is totally unacceptable. We should not have been able to affect production at this scale, and our existing safeguards failed to contain the incident. We take full responsibility for this failure. The root cause was not an individual action, but gaps in our systems, tooling, and processes that allowed a small error to escalate into a broad outage. We are already acting on multiple fronts to prevent any forms of recurrence, with some corrective measures already in place and others actively in progress (see above). These changes are focused on preventing similar mistakes from reaching production, limiting how far mistakes can propagate and improving recovery behavior to be safer and more predictable. As always, feel free to contact us in case you need anything. We’re committed to doing better..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>12:10:35</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>13:13:44</var> GMT+0</small><br><strong>Identified</strong> - We are working on a fix, you may resume your services to recover your service faster. We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>14:47:12</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. The majority of the services have been recovered; we are still recovering some of the free services..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>16:06:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 20 Dec 2025 12:10:35 +0000 https://status.koyeb.com/incident/cmje9b49j01ke5pknjd294wgi https://status.koyeb.com/incident/cmje9b49j01ke5pknjd294wgi Update service issue for docker based deployment Type: Incident Duration: 4 hours and 20 minutes Affected Components: Build / Provisioning, Control Panel Dec 20, 14:13:08 GMT+0 - Resolved - This incident has been resolved. Dec 20, 09:52:44 GMT+0 - Investigating - We received reports preventing to create or update docker deployments. We are currently investigating this incident. Dec 20, 10:19:16 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 4 hours and 20 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>14:13:08</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>09:52:44</var> GMT+0</small><br><strong>Investigating</strong> - We received reports preventing to create or update docker deployments. We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>10:19:16</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Sat, 20 Dec 2025 09:52:44 +0000 https://status.koyeb.com/incident/cmje4duvx00hr5pknvdlek6l1 https://status.koyeb.com/incident/cmje4duvx00hr5pknvdlek6l1 Deployment delay Type: Incident Duration: 37 minutes Affected Components: Build / Provisioning, API Dec 10, 15:51:18 GMT+0 - Investigating - We are currently investigating this incident. Dec 10, 16:28:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 37 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>15:51:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 10</var>, <var data-var='time'>16:28:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 10 Dec 2025 15:51:18 +0000 https://status.koyeb.com/incident/cmj06sft00077hgixbfto1lj5 https://status.koyeb.com/incident/cmj06sft00077hgixbfto1lj5 Login issue and provisioning delay Type: Incident Duration: 19 minutes Affected Components: Control Panel, Build / Provisioning Dec 5, 08:58:56 GMT+0 - Identified - We are currently investigating this incident, it seems to be related to an outage from Cloudflare <https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q> . Login and signup is unavailable, provisioning might be deleted. We have not noticed any issues on running services so far. Dec 5, 09:13:39 GMT+0 - Monitoring - A fix has been issued by Cloudflare, we are monitoring. Dec 5, 09:17:41 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 19 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>08:58:56</var> GMT+0</small><br><strong>Identified</strong> - We are currently investigating this incident, it seems to be related to an outage from Cloudflare <https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q> . Login and signup is unavailable, provisioning might be deleted. We have not noticed any issues on running services so far..</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:13:39</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been issued by Cloudflare, we are monitoring..</p> <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>09:17:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 5 Dec 2025 08:58:56 +0000 https://status.koyeb.com/incident/cmismuvgc01h5zr3vf5etzg9b https://status.koyeb.com/incident/cmismuvgc01h5zr3vf5etzg9b Provisioning delays Type: Incident Duration: 3 hours and 11 minutes Affected Components: Frankfurt - FRA, , , San Francisco - SFO, Washington, D.C. - WAS, Paris - PAR, Europe → North America → Dec 4, 00:53:41 GMT+0 - Identified - We identified the issue in North America. We are working on a fix Dec 4, 01:41:34 GMT+0 - Resolved - This incident has been resolved. Dec 3, 22:30:17 GMT+0 - Investigating - We are aware of new deployments being stuck provisioning. Deployments in deep sleep are also affected and may fail waking up. Dec 3, 23:16:17 GMT+0 - Investigating - We are currently investigating this incident. Dec 3, 23:57:38 GMT+0 - Identified - Frankfurt and Paris have recovered. We are still investigating the issue in North America Type: Incident

Duration: 3 hours and 11 minutes

Affected Components: , , , , ,

<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>00:53:41</var> GMT+0</small><br><strong>Identified</strong> - We identified the issue in North America. We are working on a fix.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>01:41:34</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>22:30:17</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of new deployments being stuck provisioning. Deployments in deep sleep are also affected and may fail waking up..</p> <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>23:16:17</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>23:57:38</var> GMT+0</small><br><strong>Identified</strong> - Frankfurt and Paris have recovered. We are still investigating the issue in North America.</p> ]]> Wed, 3 Dec 2025 22:30:17 +0000 https://status.koyeb.com/incident/cmiqnoehv02kjbm3z3ars3zkk https://status.koyeb.com/incident/cmiqnoehv02kjbm3z3ars3zkk Provisioning delays Type: Incident Duration: 22 minutes Affected Components: Paris - PAR Nov 26, 09:31:57 GMT+0 - Investigating - We are aware of an issue slowing down deployments in Paris. Other regions are not affected. Nov 26, 09:53:56 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 22 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>09:31:57</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of an issue slowing down deployments in Paris. Other regions are not affected..</p> <p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>09:53:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 26 Nov 2025 09:31:57 +0000 https://status.koyeb.com/incident/cmift2nic011oot8x87h2lo35 https://status.koyeb.com/incident/cmift2nic011oot8x87h2lo35 High rate of 502 Type: Incident Duration: 4 hours and 6 minutes Affected Components: Frankfurt - FRA, , Tokyo - TYO, Singapore - SIN, , San Francisco - SFO, Washington, D.C. - WAS, , Paris - PAR, Europe → North America → Asia–Pacific - APAC → Nov 18, 11:48:09 GMT+0 - Investigating - We are currently investigating this incident. It seems related to Cloudflare ongoing outage <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7> Nov 18, 15:22:39 GMT+0 - Monitoring - Cloudflare implemented a fix, we are seeing some improvements. We are still monitoring the situation. Nov 18, 15:53:42 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 hours and 6 minutes

Affected Components: , , , , , , , ,

<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:48:09</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. It seems related to Cloudflare ongoing outage <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7>.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>15:22:39</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare implemented a fix, we are seeing some improvements. We are still monitoring the situation..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>15:53:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 18 Nov 2025 11:48:09 +0000 https://status.koyeb.com/incident/cmi4if06702apvfvv8t6y6anm https://status.koyeb.com/incident/cmi4if06702apvfvv8t6y6anm App downtime in Singapore Type: Incident Duration: 3 hours and 47 minutes Affected Components: Singapore - SIN Nov 10, 04:21:00 GMT+0 - Investigating - We are currently investigating and issue where some apps are down in Singapore. In case this is affecting your app, the current workaround is to deploy to another region, e.g. Tokyo. Nov 10, 05:57:43 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 10, 08:08:19 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 47 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>04:21:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating and issue where some apps are down in Singapore. In case this is affecting your app, the current workaround is to deploy to another region, e.g. Tokyo..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>05:57:43</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>08:08:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 10 Nov 2025 04:21:00 +0000 https://status.koyeb.com/incident/cmhsnqsj7002askf57kcv2x77 https://status.koyeb.com/incident/cmhsnqsj7002askf57kcv2x77 Elevated rate of 502 on some services in FRA Type: Incident Duration: 31 minutes Affected Components: Frankfurt - FRA Oct 27, 09:32:42 GMT+0 - Investigating - We are currently investigating this incident. Oct 27, 09:47:28 GMT+0 - Monitoring - This seems to be related to a single host, the workload were automatically re-ballanced. We're monitoring the situation. Oct 27, 10:03:13 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 31 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>09:32:42</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>09:47:28</var> GMT+0</small><br><strong>Monitoring</strong> - This seems to be related to a single host, the workload were automatically re-ballanced. We're monitoring the situation. .</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>10:03:13</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 27 Oct 2025 09:32:42 +0000 https://status.koyeb.com/incident/cmh8xw2ir00ku7lmxjobja0rf https://status.koyeb.com/incident/cmh8xw2ir00ku7lmxjobja0rf Network upgrade on one A100 hypervisor in NA Type: Maintenance Duration: 30 minutes Affected Components: , San Francisco - SFO, Washington, D.C. - WAS, North America → 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. Oct 7, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 7, 19:30:00 GMT+0 - Completed - Maintenance is now in progress Type: Maintenance

Duration: 30 minutes

Affected Components: , ,

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. We will be performing some network operations..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is now in progress.</p> ]]> Tue, 7 Oct 2025 19:00:00 +0000 https://status.koyeb.com/maintenance/cmggqn1lb01k3a2qnwavj1sav https://status.koyeb.com/maintenance/cmggqn1lb01k3a2qnwavj1sav 503s in Singapore, Tokyo and Washington Type: Incident Duration: 1 hour and 3 minutes Affected Components: Singapore - SIN, Tokyo - TYO, Washington, D.C. - WAS Sep 27, 03:00:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 27, 03:53:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 27, 04:03:14 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 3 minutes

Affected Components: , ,

<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:53:38</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>04:03:14</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 27 Sep 2025 03:00:00 +0000 https://status.koyeb.com/incident/cmg1oo2td03w42xojyivafd9o https://status.koyeb.com/incident/cmg1oo2td03w42xojyivafd9o All regions unavailable for some time Type: Incident Duration: 2 hours and 9 minutes Affected Components: , Paris - PAR, Singapore - SIN, Washington, D.C. - WAS, Tokyo - TYO, , San Francisco - SFO, Frankfurt - FRA, , Europe → North America → Asia–Pacific - APAC → Sep 8, 11:31:44 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 8, 11:27:35 GMT+0 - Investigating - We are currently investigating this incident. Sep 8, 13:01:55 GMT+0 - Monitoring - The configuration was rolled back; we're still seeing and monitoring a few unhealthy deployments for the free users. Some new deployments might be throttled due to the volume of new instance creation caused by the rescheduling. Sep 8, 13:37:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 9 minutes

Affected Components: , , , , , , , ,

<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>11:31:44</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>11:27:35</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>13:01:55</var> GMT+0</small><br><strong>Monitoring</strong> - The configuration was rolled back; we're still seeing and monitoring a few unhealthy deployments for the free users. Some new deployments might be throttled due to the volume of new instance creation caused by the rescheduling..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>13:37:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 8 Sep 2025 11:27:35 +0000 https://status.koyeb.com/incident/cmfb1f2iw000xi0nw0gst3v7m https://status.koyeb.com/incident/cmfb1f2iw000xi0nw0gst3v7m Network maintenance in SFO Type: Incident Duration: 1 hour and 40 minutes Affected Components: San Francisco - SFO Aug 26, 06:15:00 GMT+0 - Identified - Our provider is currently performing some network maintenance in the region, and we're noticing some network disruption. Aug 26, 07:54:42 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 40 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Identified</strong> - Our provider is currently performing some network maintenance in the region, and we're noticing some network disruption..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>07:54:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 26 Aug 2025 06:15:00 +0000 https://status.koyeb.com/incident/cmes6n1lc005hg357t3xst1eh https://status.koyeb.com/incident/cmes6n1lc005hg357t3xst1eh Network disruption causing 503 Type: Incident Duration: 10 minutes Affected Components: , Paris - PAR, Singapore - SIN, , Washington, D.C. - WAS, San Francisco - SFO, Tokyo - TYO, Frankfurt - FRA, , Europe → North America → Asia–Pacific - APAC → Aug 19, 16:54:16 GMT+0 - Resolved - This incident has been resolved. Aug 19, 16:44:15 GMT+0 - Investigating - We are currently investigating this incident. Aug 19, 16:48:48 GMT+0 - Monitoring - This was most likely caused by a DDOS, we've blocked the source, and are investigating the issue. Traffic should be back to normal. Type: Incident

Duration: 10 minutes

Affected Components: , , , , , , , ,

<p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>16:54:16</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>16:44:15</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>16:48:48</var> GMT+0</small><br><strong>Monitoring</strong> - This was most likely caused by a DDOS, we've blocked the source, and are investigating the issue. Traffic should be back to normal..</p> ]]> Tue, 19 Aug 2025 16:44:15 +0000 https://status.koyeb.com/incident/cmeirx9bb000120nfu7ri6dec https://status.koyeb.com/incident/cmeirx9bb000120nfu7ri6dec Paris datacenter migraiton Type: Maintenance Duration: 1 day, 3 hours and 22 minutes Affected Components: Paris - PAR 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 Mar 11, 14:17:09 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 1 day, 3 hours and 22 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>10:57:10</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>10:55:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. There should be no downtime during that time.</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>14:17:09</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 10 Mar 2025 10:55:00 +0000 https://status.koyeb.com/maintenance/cm82y4u9i0001btb9b8v2f70n https://status.koyeb.com/maintenance/cm82y4u9i0001btb9b8v2f70n San Francisco datacenter migraiton Type: Maintenance Affected Components: San Francisco - SFO 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. Type: Maintenance

Affected Components:

<p><small>Feb <var data-var='date'> 14</var>, <var data-var='time'>10:05:25</var> GMT+0</small><br><strong>Completed</strong> - 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..</p> ]]> Fri, 14 Feb 2025 10:05:25 +0000 https://status.koyeb.com/maintenance/cm74m75vl008913m6xru8m0lt https://status.koyeb.com/maintenance/cm74m75vl008913m6xru8m0lt Migration to new network stack Type: Maintenance Duration: 3 hours and 39 minutes Affected Components: Frankfurt - FRA Oct 7, 14:14:22 GMT+0 - Completed - Maintenance has completed successfully. 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. Oct 7, 10:35:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 3 hours and 39 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>14:14:22</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>10:35:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>10:35:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Mon, 7 Oct 2024 10:35:00 +0000 https://status.koyeb.com/maintenance/cm1yvils3002311yszoxfzcop https://status.koyeb.com/maintenance/cm1yvils3002311yszoxfzcop Migration to new network stack Type: Maintenance Duration: 3 hours and 54 minutes Affected Components: Washington, D.C. - WAS 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. Oct 7, 08:53:01 GMT+0 - Identified - Maintenance is now in progress Oct 7, 12:47:25 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 3 hours and 54 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>08:53:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>08:53:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>12:47:25</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Mon, 7 Oct 2024 08:53:00 +0000 https://status.koyeb.com/maintenance/cm1yrwnmu00024fbm5fccmhot https://status.koyeb.com/maintenance/cm1yrwnmu00024fbm5fccmhot Migration to new network stack Type: Maintenance Duration: 2 days, 11 hours and 1 minute Affected Components: Frankfurt - FRA Oct 4, 19:53:16 GMT+0 - Completed - Maintenance has completed successfully. 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. Oct 2, 08:52:40 GMT+0 - Identified - Maintenance is now in progress. Type: Maintenance

Duration: 2 days, 11 hours and 1 minute

Affected Components:

<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>19:53:16</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>08:51:56</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>08:52:40</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> ]]> Wed, 2 Oct 2024 08:51:56 +0000 https://status.koyeb.com/maintenance/cm1rmq0430038bhnij7xz7cjp https://status.koyeb.com/maintenance/cm1rmq0430038bhnij7xz7cjp Migration to network stack v2 Type: Maintenance Duration: 2 hours and 12 minutes Affected Components: Washington, D.C. - WAS 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. 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. Type: Maintenance

Duration: 2 hours and 12 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>14:45:06</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>14:47:44</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> ]]> Thu, 26 Sep 2024 14:45:06 +0000 https://status.koyeb.com/maintenance/cm1jero3u0002v26njit3cmzj https://status.koyeb.com/maintenance/cm1jero3u0002v26njit3cmzj Migration to network stack v2 Type: Maintenance Duration: 3 hours and 10 minutes Affected Components: Tokyo - TYO Sep 13, 20:25:01 GMT+0 - Completed - Maintenance has completed successfully. 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. Sep 13, 17:14:43 GMT+0 - Identified - Maintenance is now in progress. Type: Maintenance

Duration: 3 hours and 10 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>20:25:01</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>17:14:17</var> GMT+0</small><br><strong>Identified</strong> - The migration will automatically trigger a redeployment of your services running in Tokyo with 60 seconds of connectivity loss at most..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>17:14:43</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> ]]> Fri, 13 Sep 2024 17:14:17 +0000 https://status.koyeb.com/maintenance/cm10zanpu00044aw9zlupq7er https://status.koyeb.com/maintenance/cm10zanpu00044aw9zlupq7er Migration to network stack v2 Type: Maintenance Duration: 1 hour and 46 minutes Affected Components: San Francisco - SFO 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. Sep 13, 16:47:48 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 1 hour and 46 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>15:01:21</var> GMT+0</small><br><strong>Identified</strong> - The migration will automatically trigger a redeployment of your services running in San Francisco with 60 seconds of connectivity loss at most..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>16:47:48</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Fri, 13 Sep 2024 15:01:21 +0000 https://status.koyeb.com/maintenance/cm10ulrao000ztlq4s79buta2 https://status.koyeb.com/maintenance/cm10ulrao000ztlq4s79buta2 Database update Type: Maintenance Duration: 2 hours Affected Components: API, Control Panel 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. 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 Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Oct <var data-var='date'> 17</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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. .</p> <p><small>Oct <var data-var='date'> 17</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Oct <var data-var='date'> 17</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 17 Oct 2023 08:00:00 +0000 https://status.koyeb.com/maintenance/clnu11xh01915bkoovar9r77o https://status.koyeb.com/maintenance/clnu11xh01915bkoovar9r77o Runtime and build logs maintenance Type: Maintenance Duration: 27 minutes Affected Components: API 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. Type: Maintenance

Duration: 27 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>15:16:51</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>14:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Fri, 6 Oct 2023 14:50:00 +0000 https://status.koyeb.com/maintenance/clnepwjpl20124bmololt7meab https://status.koyeb.com/maintenance/clnepwjpl20124bmololt7meab Core database update Type: Maintenance Duration: 1 hour Affected Components: API, Control Panel 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. Type: Maintenance

Duration: 1 hour

Affected Components: ,

<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>12:00:14</var> GMT+0</small><br><strong>Completed</strong> - The maintenance is now completed..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>11:00:34</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>12:25:22</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Tue, 2 May 2023 11:00:00 +0000 https://status.koyeb.com/maintenance/clhj42pzx0004srmzbxwlfn33-k73xllkwdw6v https://status.koyeb.com/maintenance/clhj42pzx0004srmzbxwlfn33-k73xllkwdw6v Core database update Type: Maintenance Duration: 1 hour Affected Components: API, Control Panel Dec 14, 14:31:43 GMT+0 - Completed - Update went smoothly, everything is back to normal. 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. Dec 14, 14:00:42 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Type: Maintenance

Duration: 1 hour

Affected Components: ,

<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>14:31:43</var> GMT+0</small><br><strong>Completed</strong> - Update went smoothly, everything is back to normal..</p> <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>13:00:28</var> GMT+0</small><br><strong>Identified</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>10:51:47</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>14:00:42</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> ]]> Wed, 14 Dec 2022 14:00:00 +0000 https://status.koyeb.com/maintenance/clhj42pzx0010srmz8a5ngoxe-tbrsw463ftb8 https://status.koyeb.com/maintenance/clhj42pzx0010srmz8a5ngoxe-tbrsw463ftb8 Core databases update Type: Maintenance Duration: 30 minutes Affected Components: API, Control Panel 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. Nov 25, 17:15:24 GMT+0 - Completed - The scheduled maintenance has been completed. Type: Maintenance

Duration: 30 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>16:45:41</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>16:18:15</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Nov <var data-var='date'> 25</var>, <var data-var='time'>17:15:24</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> ]]> Fri, 25 Nov 2022 16:45:00 +0000 https://status.koyeb.com/maintenance/clhj42pzx0015srmz6xoch2xx-x75l9w20g4tx https://status.koyeb.com/maintenance/clhj42pzx0015srmz6xoch2xx-x75l9w20g4tx Core platform update Type: Maintenance Duration: 3 hours Affected Components: API, Control Panel Oct 12, 17:55:45 GMT+0 - Completed - The scheduled maintenance has been completed. 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. Oct 12, 14:00:52 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. 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. Type: Maintenance

Duration: 3 hours

Affected Components: ,

<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>17:55:45</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>12:26:30</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>14:00:52</var> GMT+0</small><br><strong>Identified</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>17:54:32</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is still in progress. We will provide updates as necessary..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>15:00:40</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> ]]> Wed, 12 Oct 2022 15:00:00 +0000 https://status.koyeb.com/maintenance/clhj42pzx0019srmze1u2cm8z-qqqhl186ctkz https://status.koyeb.com/maintenance/clhj42pzx0019srmze1u2cm8z-qqqhl186ctkz Core databases update Type: Maintenance Duration: 2 hours Affected Components: API, Control Panel Sep 13, 09:00:33 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 13, 10:17:27 GMT+0 - Identified - Verification is currently underway for the maintenance items. Sep 13, 08:00:23 GMT+0 - Identified - Maintenance will begin as scheduled in 60 minutes. Sep 13, 11:01:20 GMT+0 - Completed - The scheduled maintenance has been completed. 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. Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>09:00:33</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>10:17:27</var> GMT+0</small><br><strong>Identified</strong> - Verification is currently underway for the maintenance items..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>08:00:23</var> GMT+0</small><br><strong>Identified</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>Sep <var data-var='date'> 13</var>, <var data-var='time'>11:01:20</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>14:47:08</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Tue, 13 Sep 2022 09:00:00 +0000 https://status.koyeb.com/maintenance/clhj42pzx001isrmzag5ofeqe-cn9mfmfp0nzq https://status.koyeb.com/maintenance/clhj42pzx001isrmzag5ofeqe-cn9mfmfp0nzq Network maintenance Type: Maintenance Duration: 2 hours Affected Components: , Europe → 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). Mar 16, 17:35:23 GMT+0 - Completed - The scheduled maintenance has been completed. Type: Maintenance

Duration: 2 hours

Affected Components:

<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>14:40:18</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>14:34:10</var> GMT+0</small><br><strong>Identified</strong> - We will perform a network update to improve performances and provide new services such as websocket and custom domains (coming soon)..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>17:35:23</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> ]]> Wed, 16 Mar 2022 15:35:00 +0000 https://status.koyeb.com/maintenance/clhj42pzy0025srmz4qyr3izw-dvv7llpw0sck https://status.koyeb.com/maintenance/clhj42pzy0025srmz4qyr3izw-dvv7llpw0sck Core platform update Type: Maintenance Duration: 2 hours Affected Components: API, Control Panel 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. Mar 16, 12:30:23 GMT+0 - Completed - The scheduled maintenance has been completed. Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>09:28:24</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>09:28:00</var> GMT+0</small><br><strong>Identified</strong> - We are performing a maintenance on one of our core platform component. Provisioning of new service might be impacted for a few minutes..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>12:30:23</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> ]]> Wed, 16 Mar 2022 10:30:00 +0000 https://status.koyeb.com/maintenance/clhj42pzy002asrmz8had148r-d1p7kgwrpcq4 https://status.koyeb.com/maintenance/clhj42pzy002asrmz8had148r-d1p7kgwrpcq4