- Level
- confirmed
- Worst impact
- Maintenance
- Regions
- eu
What to do
Check whether you use Koyeb in eu. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Check that everything you run on Koyeb came back after the window closed 2026-02-09 01:00 UTC.
Subscribe to Koyeb's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=koyeb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Koyeb 1
- resolved
Type: Maintenance Duration: 21 hours and 45 minutes Affected Components: Frankfurt - FRA, Paris - PAR, Europe → Feb 9, 22:45:07 GMT+0 - Completed - Maintenance has completed successfully. Feb 9, 13:00:00 GMT+0 - Identified - Maintenance has completed successfully Feb 9, 01:00:01 GMT+0 - Identified - Maintenance is now in progress 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**.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-98c4860156
Is this Koyeb maintenance still going on?
No, it ended 2026-02-09 01:00 UTC.
How long did it last?
0m, from 2026-02-09 01:00 UTC to 2026-02-09 01:00 UTC, by the times Koyeb posted.
What was affected?
Koyeb named in eu.
What caused it?
Koyeb hasn't published a root cause. If it does, it shows here.
Where does this come from?
Koyeb's official status page, https://status.koyeb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.