Skip to main content
env0

Renewed AWS Outage Causing Widespread Service Disruption

Partial outage Lasted 0m · started · env0's page

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 16:01 UTC and 2025-10-20 16:01 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

  1. resolved

    Type: Incident Affected Components: API, Management Console Oct 20, 22:45:08 GMT+0 - Resolved - This incident has been resolved. Oct 20, 16:01:14 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Oct 20, 16:01:00 GMT+0 - Monitoring - We are currently monitoring a widespread service disruption affecting our system. This incident is caused by a significant, ongoing network connectivity outage in AWS's US-EAST-1 Region, which is impacting multiple services including EC2, DynamoDB, and SQS. Our team is in contact with our provider and actively monitoring the situation. We will post an update as soon as AWS provides more information on their recovery.

    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-c47c7dafcc

Is env0 still down?

No, this incident was resolved 2025-10-20 16:01 UTC. For env0's live state, see https://down.guide/env0.

How long did it last?

0m, from 2025-10-20 16:01 UTC to 2025-10-20 16:01 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.