Koyeb Outage History

Koyeb partial outage View live status →

Koyeb had 35 outages in the last 2 years — averaging 1.4 incidents per month.

There were 35 Koyeb outages since October 7, 2024. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.koyeb.com

Minor October 7, 2025

Network upgrade on one A100 hypervisor in NA

Detected by Pingoru
Oct 07, 2025, 07:00 PM UTC
Resolved
Oct 07, 2025, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 07, 2025, 07:00 PM UTC

    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

Read the full incident report →

Minor March 10, 2025

Paris datacenter migraiton

Detected by Pingoru
Mar 10, 2025, 10:55 AM UTC
Resolved
Mar 10, 2025, 10:55 AM UTC
Duration
Timeline · 1 update
  1. resolved Mar 10, 2025, 10:55 AM UTC

    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.

Read the full incident report →

Minor February 14, 2025

San Francisco datacenter migraiton

Detected by Pingoru
Feb 14, 2025, 10:05 AM UTC
Resolved
Feb 14, 2025, 10:05 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 14, 2025, 10:05 AM UTC

    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.

Read the full incident report →