- Level
- confirmed
- Worst impact
- Degraded
- Components
- Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN, Frankfurt - FRA
- Regions
- apac, eu
- Down Index
- 16of 100
What to do
Check whether you use Koyeb Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN and 1 more in apac, 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-07-21 09:30 UTC and 2026-07-21 09:30 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 59 minutes Affected Components: Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN, Frankfurt - FRA Jul 21, 11:29:00 GMT+0 - Resolved - This incident has been resolved. Jul 21, 09:30:00 GMT+0 - Investigating - We had an issue where new custom domains or refreshed custom domains would be stuck in Pending.
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-14709520fa
Is Koyeb still down?
No, this incident was resolved 2026-07-21 09:30 UTC. For Koyeb's live state, see https://down.guide/koyeb.
How long did it last?
0m, from 2026-07-21 09:30 UTC to 2026-07-21 09:30 UTC, by the times Koyeb posted.
What was affected?
Koyeb named Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN and 1 more in apac, 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.