Investigating issues with Microsoft private saas environments.


Microsoft RCA report: The Engineering Team has explained to us that the there is no performance counters indicating what exactly is wrong, except they can only see the bare minimum CPU and memory counters.

The root cause of the incident has been due to the Global NST Log trying to reload the base CLR objects over and over again.

There is no evidence of this happening before, so it's rare and the Engineers believe the performance issue was due to extra time spent on loading metadata.


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


We are still trying to identify the root cause of the issue with Microsoft.


We regret to inform you that we are currently unable to provide any further updates regarding the ongoing issue. Microsoft is working on it for a solution.


We have escalated the issue to Microsoft for further assistance. Our team is actively collaborating with them to address and resolve the issue. We will provide updates as soon as new information becomes available. Thank you for your understanding and patience.


We have verified the presence of an issue within the private cloud environment and are currently engaged in resolving it. Please note that this problem is specific to the private cloud environment. We are actively updating the status page to reflect the current situation. Thank you for your patience as we work to resolve this issue.


Currently, certain customers are encountering issues with our service. The problem revolves around our app platform specifically for Microsoft private cloud customers. The following customers may be affected: 038, 043, 095, 112, 123, 138, 144, 146, 152, 155, 164, 190, 203, 210, 217, 225, 228, 230, 233, 246, 250, 251, 256, and 264. Our team is actively working towards resolving this situation as quickly as we can.

Began at:

Affected components
  • Environments
    • Microsoft (private) Cloud