- Level
- confirmed
- Worst impact
- Degraded
- Components
- Frankfurt - FRA
- Regions
- eu
- Down Index
- 12of 100
What to do
Check whether you use Koyeb Frankfurt - FRA 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.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-05-26 18:47 UTC and 2026-05-26 18:47 UTC may need a replay.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: Incident Duration: 18 hours and 24 minutes Affected Components: Frankfurt - FRA May 27, 13:11:30 GMT+0 - Resolved - This incident has been resolved. May 26, 18:47:22 GMT+0 - Identified - We are investigating the possible loss of an hypervisor node. We will update you as soon as we have more information.
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-e1dbffc4ae
Is Koyeb still down?
No, this incident was resolved 2026-05-26 18:47 UTC. For Koyeb's live state, see https://down.guide/koyeb.
How long did it last?
0m, from 2026-05-26 18:47 UTC to 2026-05-26 18:47 UTC, by the times Koyeb posted.
What was affected?
Koyeb named Frankfurt - FRA 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.