Koyeb: Provisioning delays

What to do

Check whether you use Koyeb Build / Provisioning in apac. 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-14 22:32 UTC and 2026-05-14 22:32 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.

resolvedMay 14, 2026, 10:32 PM UTC
Type: Incident Duration: 4 hours and 23 minutes Affected Components: Build / Provisioning May 15, 02:55:07 GMT+0 - Resolved - We are happy with the fix. Tokyo may still have a some delay but will be promptly resolved as well. May 15, 02:40:20 GMT+0 - Monitoring - We implemented a fix in Tokyo and are currently monitoring the result. May 15, 02:17:00 GMT+0 - Identified - Most regions are back to normal, but Tokyo is still lagging behind. We are still working on a fix for Tokyo region May 14, 22:50:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 14, 22:32:18 GMT+0 - Investigating - We are currently investigating this incident.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Koyeb still down?

No, this incident was resolved 2026-05-14 22:32 UTC. For Koyeb's live state, see https://down.guide/koyeb.

How long did it last?

0m, from 2026-05-14 22:32 UTC to 2026-05-14 22:32 UTC, by the times Koyeb posted.

What was affected?

Koyeb named Build / Provisioning in apac.

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.