- Level
- confirmed
- Worst impact
- Degraded
- Components
- Managed Deployment Workers
- Down Index
- 8of 100
What to do
Check whether you use env0 Managed Deployment Workers. 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-05 07:39 UTC and 2026-07-05 07:39 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 Duration: 1 hour and 45 minutes Affected Components: Managed Deployment Workers Jul 5, 09:23:53 GMT+0 - Resolved - This incident has been resolved. Jul 5, 08:16:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 5, 07:39:00 GMT+0 - Identified - We have identified the root cause of delayed deployments. Our team is actively working on a fix. Deployments are queuing and will process once the fix is in place — no action is needed on your side. Next update in 30 minutes.
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-a76ea3154c
Is env0 still down?
No, this incident was resolved 2026-07-05 07:39 UTC. For env0's live state, see https://down.guide/env0.
How long did it last?
0m, from 2026-07-05 07:39 UTC to 2026-07-05 07:39 UTC, by the times env0 posted.
What was affected?
env0 named Managed Deployment Workers.
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.