- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API
- Down Index
- 18of 100
What to do
Check whether you use env0 API. 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-01-13 10:29 UTC and 2026-01-13 10:29 UTC may need a replay.Subscribe to env0's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=env0 works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from env0 1
- resolved
Type: Incident Affected Components: API Jan 13, 12:08:38 GMT+0 - Resolved - The issue was caused by a deployment mechanism failure, where one of the services did not deploy successfully while other services attempted to call newly introduced functions. Jan 13, 10:43:49 GMT+0 - Monitoring - We identified the issue and applied a quick fix. The system has returned to normal operation. We are continuing to monitor for any additional errors. Jan 13, 10:29:15 GMT+0 - Identified - The issue has been identified and a fix is being implemented.
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-bfb1fa081b
Is env0 still down?
No, this incident was resolved 2026-01-13 10:29 UTC. For env0's live state, see https://down.guide/env0.
How long did it last?
0m, from 2026-01-13 10:29 UTC to 2026-01-13 10:29 UTC, by the times env0 posted.
What was affected?
env0 named API.
What caused it?
env0 hasn't published a root cause. If it does, it shows here.
Where does this come from?
env0's official status page, https://status.env0.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.