Is Koyeb down?
Last checked 4m agoNo incidents right now.
Koyeb is operational right now. Last checked 4m ago; the most recent incident resolved 15d ago.
Real-time Koyeb status, recent outages, and incident history: pulled directly from Koyeb's official status page at status.koyeb.com every 5 minutes. Pingoru tracks 17 Koyeb services and has captured 21 incidents in the last 90 days (99.02% uptime). Get email, Slack, Discord, or webhook alerts the moment Koyeb reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Control PanelAPIBuild / Provisioning
Timeline · 3 updates
- identified · Oct 16, 2026, 07:36 AM UTC
The ongoing maintenance is causing API to fail with 500. This was expected, but the duration seems to be longer than what we were expecting.
- monitoring · Oct 16, 2026, 07:51 AM UTC
We implemented a fix and are currently monitoring the result.
- resolved · Oct 16, 2026, 08:01 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 3 updates
- identified · Oct 16, 2026, 07:36 AM UTC
The ongoing maintenance is causing API to fail with 500. This was expected, but the duration seems to be longer than what we were expecting..
- monitoring · Oct 16, 2026, 07:51 AM UTC
We implemented a fix and are currently monitoring the result..
- resolved · Oct 16, 2026, 08:01 AM UTC
This incident has been resolved..
Latest: This incident has been resolved..
-
- Washington, D.C. - WAS
Timeline · 2 updates
- 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.
- resolved · Sep 29, 2026, 01:45 PM UTC
The provider had a networking issue that was resolved. The capacity is now back to normal.
Latest: The provider had a networking issue that was resolved. The capacity is now back to normal.
-
-
Timeline · 2 updates
- 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..
- resolved · Sep 29, 2026, 01:45 PM UTC
The provider had a networking issue that was resolved. The capacity is now back to normal..
Latest: The provider had a networking issue that was resolved. The capacity is now back to normal..
-
- API
Timeline · 2 updates
- 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.
- resolved · Sep 29, 2026, 09:37 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Koyeb outage history
14 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Koyeb outage history →Or sign up free to get alerts when Koyeb breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · Instatus · 17 components checked every 5 minutesThe longest incident in the last year, Hypervisor unavailable on May 25, 2026, ran for 21 hours. 3 maintenance windows announced in the same period.
Most affected components, last 12 months
- Overall25
- Build / Provisioning14
- API6
- Frankfurt - FRA6
- Washington, D.C. - WAS5
Latest incidents
- 500 errors in the API and control panel, delay in provisioning
The ongoing maintenance is causing API to fail with 500. This was expected, but the duration seems to be longer than what we were expecting.
- 500 errors in the API and control panel, delay in provisioning
The ongoing maintenance is causing API to fail with 500. This was expected, but the duration seems to be longer than what we were expecting..
- Low availabilty on was1
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…
- Started Oct 16, 2026, 07:36 AM UTC · Resolved Oct 16, 2026, 08:01 AM UTC · 24m
- Started Oct 16, 2026, 07:36 AM UTC · Resolved Oct 16, 2026, 08:01 AM UTC · 24m
- Low availabilty on was1 ResolvedStarted Sep 29, 2026, 01:16 PM UTC · Resolved Sep 29, 2026, 01:45 PM UTC · 28m
- Low availabilty on was1 ResolvedStarted Sep 29, 2026, 01:16 PM UTC · Resolved Sep 29, 2026, 01:45 PM UTC · 28m
- Provisioning error for new services ResolvedStarted Sep 29, 2026, 08:46 AM UTC · Resolved Sep 29, 2026, 09:37 AM UTC · 51m
- Provisioning error for new services ResolvedStarted Sep 29, 2026, 08:46 AM UTC · Resolved Sep 29, 2026, 09:37 AM UTC · 51m
- API timing out ResolvedStarted Sep 23, 2026, 03:53 PM UTC · Resolved Sep 23, 2026, 04:38 PM UTC · 44m
- API timing out ResolvedStarted Sep 23, 2026, 03:53 PM UTC · Resolved Sep 23, 2026, 04:38 PM UTC · 44m