Notice history -

Resolved
March 10, 2026 at 11:15 AM
Resolved
March 10, 2026 at 11:15 AM
The issue affecting OIDC-based AWS deployments has been resolved. All systems are operating normally. No data was lost or compromised. We apologize for the inconvenience.
Monitoring
March 10, 2026 at 11:00 AM
Monitoring
March 10, 2026 at 11:00 AM
A fix has been deployed for OIDC-based AWS deployment failures. We are monitoring to confirm full recovery. Customers using access keys or non-AWS providers were not affected. If you continue to experience issues, contact support@env0.com.
Identified
March 10, 2026 at 10:20 AM
Identified
March 10, 2026 at 10:20 AM
We have identified the root cause of the OIDC AWS deployment failures. A recent platform update introduced a change that is incompatible with some AWS IAM OIDC identity provider configurations. Our team is working on a fix.
Investigating
March 10, 2026 at 10:00 AM
Investigating
March 10, 2026 at 10:00 AM
We are investigating reports of failed AWS deployments for customers using OIDC-based authentication. Our team is actively looking into this.

No notices reported this month

Resolved
January 13, 2026 at 12:08 PM
Resolved
January 13, 2026 at 12:08 PM
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.
Monitoring
January 13, 2026 at 10:43 AM
Monitoring
January 13, 2026 at 10:43 AM
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.
Identified
January 13, 2026 at 10:29 AM
Identified
January 13, 2026 at 10:29 AM
The issue has been identified and a fix is being implemented.

Resolved
January 07, 2026 at 4:57 PM
Resolved
January 07, 2026 at 4:57 PM
This incident has been resolved.
Update
January 07, 2026 at 3:41 PM
Update
January 07, 2026 at 3:41 PM
We are continuing to monitor for any further issues.
Monitoring
January 07, 2026 at 3:39 PM
Monitoring
January 07, 2026 at 3:39 PM
We're identified some issues regarding Authentication errors, we've implemented a fix and we're monitoring the situation

- Notice history