env0 incident

OIDC AWS Deployment Failures

Minor Resolved View vendor source →
Started
Mar 10, 2026, 10:00 AM UTC
Resolved
Mar 10, 2026, 10:00 AM UTC
Duration
Detected by Pingoru
Mar 10, 2026, 10:00 AM UTC

Update timeline

  1. resolved Mar 10, 2026, 10:00 AM UTC

    Type: Incident Duration: 1 hour and 15 minutes Affected Components: Managed Deployment Workers, Self-Hosted Deployment Workers Mar 10, 10:00:00 GMT+0 - Investigating - We are investigating reports of failed AWS deployments for customers using OIDC-based authentication. Our team is actively looking into this. Mar 10, 10:20:00 GMT+0 - Identified - 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. Mar 10, 11:15:00 GMT+0 - Resolved - 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. Mar 10, 11:00:00 GMT+0 - Monitoring - 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 [[email protected]](mailto:[email protected]).

Looking to track env0 downtime and outages?

Pingoru polls env0's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when env0 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track env0 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring env0 for free

5 free monitors · No credit card required