Koyeb Outage History
7 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Koyeb Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 16, 2026 | 500 errors in the API and control panel, delay in provisioning | 25 min | Resolved |
| Oct 16, 2026 | API and provisioningScheduled Maintenance | 1h 0m | Scheduled |
| Sep 29, 2026 | Low availabilty on was1 | 1h 58m | Resolved |
| Sep 29, 2026 | Quotas not respected | 53 min | Resolved |
| Sep 23, 2026 | API timing out | 45 min | Resolved |
| Sep 22, 2026 | Builds in pending in FRA | 17 min | Resolved |
| Sep 15, 2026 | RTXA6000 currently unavailable | 6h 7m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Koyeb incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Koyeb Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Koyeb acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Koyeb outage in this window ran 6h 7m, against a mean recovery of 1h 38m. If you depend on Koyeb in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.