- Level
- confirmed
- Worst impact
- Degraded
- Components
- Washington, D.C. - WAS
- Down Index
- 10of 100
What to do
Check whether you use Koyeb Washington, D.C. - WAS. 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-09-29 13:16 UTC and 2026-09-29 13:16 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: 29 minutes Affected Components: Washington, D.C. - WAS Sep 29, 13:45:00 GMT+0 - Resolved - The provider had a networking issue that was resolved. The capacity is now back to normal. Sep 29, 13:16:01 GMT+0 - Identified - Due to an incident with a provider, we are short on capacity on was1. We are trying to restore capacity there. In the meantime, deployments in that region could be slow to be deployed. We suggest using other regions for the time being.
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-c6a9403534
Is Koyeb still down?
No, this incident was resolved 2026-09-29 13:16 UTC. For Koyeb's live state, see https://down.guide/koyeb.
How long did it last?
0m, from 2026-09-29 13:16 UTC to 2026-09-29 13:16 UTC, by the times Koyeb posted.
What was affected?
Koyeb named Washington, D.C. - WAS.
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.