- Notice history

This incident has been resolved.

A fix was rolled out successfully and we're monitoring the results

We've identified a possible cause and are looking to roll out a fix

We've rolled out the fix that will allow GitLab tokens to be refreshed. You will need to re-authenticate your using GitLab user/bot with env0 by editing the Template in env0 that integrates with that GitLab user, click the "authorize another GitLab user" and authorize with your user/bot again. Once again we're terribly sorry for the inconvenience - we're in touch with GitLab trying to understand how it came to pass that we were not alerted about this change in their API to avoid such future incidents.

GItLab.com (the Saas) updated their version to 15.x. which deprecates our authorization approach. We are working on a solution, in the meantime, if you must use GitLab you can re-authorize by going into the template, selecting "authorize another Gitlab user"

env0 deployments are at peak performance again

Deployments are now operational but may take longer to start than usual. We're still working on getting env0 back to peak performance

Deployments are now operational but may take longer to start than usual. We're still working on getting env0 back to peak performance

This incident has been resolved. If you have an environment that appears "In Progress" when it has already finish, then clicking on the "abort" button will resolve the issue.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue. Effects of this issue include slowness in deployments, inability to approve or cancel deployments

This incident has been resolved.

The issue has been resolved. All new deployments should now start as usual

The incident has been resolved. All env0 components are now fully operational

We are continuing to investigate this issue.

This incident has been resolved.

A fix has been deployed ad we're monitoring the results