env0 Outage History

env0 is up right now

env0 had 10 outages in the last 2 years — averaging 0.4 incidents per month.

There were 10 env0 outages since July 28, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.env0.com

Major January 13, 2026

VCS on-premises may be experiencing a partial outage

Detected by Pingoru
Jan 13, 2026, 10:29 AM UTC
Resolved
Jan 13, 2026, 10:29 AM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Jan 13, 2026, 10:29 AM UTC

    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.

Read the full incident report →

Minor January 7, 2026

Authentication Issues

Detected by Pingoru
Jan 07, 2026, 03:39 PM UTC
Resolved
Jan 07, 2026, 03:39 PM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Jan 07, 2026, 03:39 PM UTC

    Type: Incident Affected Components: API, Management Console Jan 7, 16:57:32 GMT+0 - Resolved - This incident has been resolved. Jan 7, 15:41:10 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Jan 7, 15:39:47 GMT+0 - Monitoring - We're identified some issues regarding Authentication errors, we've implemented a fix and we're monitoring the situation

Read the full incident report →

Major November 18, 2025

OpenTofu Module Registry is unavailable

Detected by Pingoru
Nov 18, 2025, 01:39 PM UTC
Resolved
Nov 18, 2025, 01:39 PM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Nov 18, 2025, 01:39 PM UTC

    Type: Incident Affected Components: OpenTofu Module Registry Nov 18, 15:08:15 GMT+0 - Resolved - This incident has been resolved. Nov 18, 13:39:36 GMT+0 - Monitoring - OpenTofu Module Registry is unavailable because of Cloudflare outage.

Read the full incident report →

Major October 20, 2025

Renewed AWS Outage Causing Widespread Service Disruption

Detected by Pingoru
Oct 20, 2025, 04:01 PM UTC
Resolved
Oct 20, 2025, 04:01 PM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Oct 20, 2025, 04:01 PM UTC

    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.

Read the full incident report →

Minor August 26, 2025

Degraded deployment performance

Detected by Pingoru
Aug 26, 2025, 02:51 PM UTC
Resolved
Aug 26, 2025, 02:51 PM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Aug 26, 2025, 02:51 PM UTC

    Type: Incident Affected Components: API, Management Console Aug 26, 16:35:37 GMT+0 - Resolved - The incident has been resolved, environment management and deployments are operational Aug 26, 16:17:55 GMT+0 - Monitoring - The fix has been applied and we'll continue to monitor the situation Aug 26, 16:12:47 GMT+0 - Identified - We've identified the issue and the fix is currently being applied Aug 26, 14:51:05 GMT+0 - Investigating - We're investigating environment management and slowness in the env0 system, which occurred earlier today and started again

Read the full incident report →

Minor August 21, 2025

Timeouts in deployments

Detected by Pingoru
Aug 21, 2025, 10:10 AM UTC
Resolved
Aug 21, 2025, 10:10 AM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Aug 21, 2025, 10:10 AM UTC

    Type: Incident Affected Components: Management Console Aug 21, 12:38:46 GMT+0 - Resolved - This incident has been resolved. Aug 21, 12:21:54 GMT+0 - Monitoring - We are currently monitoring the situation. The rate of delayed deployments in env0 was greatly reduced, and we are currently monitoring to make sure that everything is back to normal Aug 21, 11:51:36 GMT+0 - Identified - Please perform a hard refresh of your page as soon as possible. Aug 21, 11:09:31 GMT+0 - Identified - Our team has identified the issue. Please perform a hard refresh of your page as soon as possible. We apologize for the inconvenience. Aug 21, 10:10:14 GMT+0 - Investigating - We are currently investigating an issue where deployments in the env0 app are not starting, are delayed, or are failing with an error.

Read the full incident report →

Minor July 28, 2025

Incident with deployments in env0

Detected by Pingoru
Jul 28, 2025, 10:31 AM UTC
Resolved
Jul 28, 2025, 10:31 AM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Jul 28, 2025, 10:31 AM UTC

    Type: Incident Affected Components: Management Console Jul 28, 11:15:20 GMT+0 - Resolved - This incident has been resolved. Jul 28, 10:58:16 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Jul 28, 10:46:23 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Jul 28, 10:31:07 GMT+0 - Investigating - We are currently investigating this issue.

Read the full incident report →

Minor July 28, 2025

Issues with deployments in env0

Detected by Pingoru
Jul 28, 2025, 09:08 AM UTC
Resolved
Jul 28, 2025, 09:08 AM UTC
Duration
Affected: env0
Timeline · 1 update
  1. resolved Jul 28, 2025, 09:08 AM UTC

    Type: Incident Affected Components: Management Console Jul 28, 09:36:06 GMT+0 - Resolved - We've identified some load on our cluster earlier, it has since subsided, and the issue is now resolved. Jul 28, 09:09:41 GMT+0 - Investigating - We are continuing to investigate this issue. Jul 28, 09:08:35 GMT+0 - Investigating - We are currently investigating this issue.

Read the full incident report →