Skip to main content
Koyeb

Disruption for new deployments

Degraded Lasted 0m · started · Koyeb's page

Level
confirmed
Worst impact
Degraded
Components
Build / Provisioning
Down Index
9of 100

What to do

  • Check whether you use Koyeb Build / Provisioning. 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-06-26 23:00 UTC and 2026-06-26 23:00 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

  1. resolved

    Type: Incident Duration: 27 minutes Affected Components: Build / Provisioning Jun 27, 01:44:40 GMT+0 - Resolved - This incident has been resolved. Jun 26, 23:00:00 GMT+0 - Investigating -

    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-3358da1f18

Is Koyeb still down?

No, this incident was resolved 2026-06-26 23:00 UTC. For Koyeb's live state, see https://down.guide/koyeb.

How long did it last?

0m, from 2026-06-26 23:00 UTC to 2026-06-26 23:00 UTC, by the times Koyeb posted.

What was affected?

Koyeb named Build / Provisioning.

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.