Investigating issues with Microsoft

User Impact:Users may have been unable to access your environment.  

Final Status:The rollback has completed, and we have confirmed via diagnostic analysis that environment access has been restored.Preliminary Root Cause: A recent deployment introduced a code misconfiguration on a portion of the infrastructure responsible for environment access.Next Steps: We're reviewing our standard service update procedures to avoid similar impact in the future.

User Experience:Users may have been unable to access your environment.  

Microsoft now resolved the incident. Thanks for your patience.

All sandbox environments are working again since 15 minutes. RCA report will follow.

Title: Environment inaccessible

User Impact:Users may be unable to access your environment.

Current Status:After our investigation, we identified that a recent deployment introduced a code misconfiguration on a portion of the infrastructure responsible for environment access. We are preparing to rollback the deployment.

User Experience:Users may be unable to access your environment.

Incident Start Time: Tuesday, February 28, 2023, 6:00 AM UTC

We've now resolved the incident. Thanks for your patience.

In the last few weeks there are multiple issues in de Microsoft Cloud en especially in de Microsoft Private Cloud. We are taking this very seriously, and we will discuss this with the Microsoft department responsible for this infrastructure.

There will also be a report published regarding this incident.

Impacted environments: 038|043|095|112|123|138|144|146|152|155|159|164|190|203|210|217|225|228|230|231|233|234|246|249|250|251|256|264

We are still in contact with Microsoft, issue not yet identified.

Public SaaS is still working.

Some customers are experiencing problems with our service right now. We're so sorry about that. Please standby for further updates, and we'll be in touch as soon as we know more.

Situation: Environment down