- Level
- confirmed
- Worst impact
- Degraded
- Components
- Control Panel
- Down Index
- 9of 100
What to do
Check whether you use Koyeb Control Panel. 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-07-16 08:59 UTC and 2026-07-16 08:59 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: 1 hour and 33 minutes Affected Components: Control Panel Jul 16, 10:32:54 GMT+0 - Resolved - This incident has been resolved. Jul 16, 08:59:54 GMT+0 - Identified - The upstream provider we use for authentication is going through a major incident. Login attempts to the control panel are failing. Direct API usage through tokens is working as expected and the running workloads are not affected.
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-f1bb000f7d
Is Koyeb still down?
No, this incident was resolved 2026-07-16 08:59 UTC. For Koyeb's live state, see https://down.guide/koyeb.
How long did it last?
0m, from 2026-07-16 08:59 UTC to 2026-07-16 08:59 UTC, by the times Koyeb posted.
What was affected?
Koyeb named Control Panel.
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.