- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API, Management Console
- Regions
- us, us-east-1
- Down Index
- 26of 100
What to do
Check whether you use env0 API, Management Console in us, us-east-1. 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 2025-10-20 07:05 UTC and 2025-10-20 07:05 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, Management Console Oct 20, 12:32:16 GMT+0 - Resolved - This incident is now resolved. Our cloud provider, AWS, has confirmed recovery for the underlying SQS issue that was affecting our deployment triggers. We have verified that all services, including PR-Plan and CD deployments, are now operating normally and all queued jobs have been processed. Oct 20, 11:45:40 GMT+0 - Monitoring - We have narrowed down the scope of the performance degradation. We have confirmed that **PR-Plan and CD deployments** are not triggered. All other deployment triggers, including **UI, API, PR Comment, and scheduled tasks, are working normally.** This issue remains a direct result of the ongoing AWS outage in the US-EAST-1 Region. We are continuing to monitor the situation and will post an update as soon as performance for PR-Plan and CD deployments is restored. Oct 20, 10:57:05 GMT+0 - Monitoring - Our core deployment service is currently experiencing degraded performance. Users may experience significant delays or errors when triggering new deployments. This is a direct result of the ongoing AWS outage affecting EC2 instances in the US-EAST-1 Region. Our team is actively monitoring the situation and AWS's recovery progress. We will post an update as soon as we see performance for our deployment service return to normal. Oct 20, 09:51:26 GMT+0 - Monitoring - We are seeing significant signs of recovery. Our cloud provider, AWS, has reported that most requests are now succeeding and they are working through a backlog. Our internal end-to-end tests confirm that our application is back online and operating as expected. We are moving this incident to "Monitoring" as we continue to observe the situation to ensure full stability and recovery. We will post a final update once we are confident the issue is fully resolved. Oct 20, 07:05:31 GMT+0 - Investigating - We are currently investigating increased error rates. We have identified a potential service disruption with our cloud provider, AWS, that we suspect is the root cause. Our team is actively monitoring the situation and working to confirm the full impact.
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-eda36db312
Is env0 still down?
No, this incident was resolved 2025-10-20 07:05 UTC. For env0's live state, see https://down.guide/env0.
How long did it last?
0m, from 2025-10-20 07:05 UTC to 2025-10-20 07:05 UTC, by the times env0 posted.
What was affected?
env0 named API, Management Console in us, us-east-1.
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.