Slow Performance and Automation

Incident Report for Moodys

Postmortem

Summary
We experienced a temporary service slowdown that impacted automation processing for some customers. The issue was caused by a sudden increase in workload that exceeded the system’s current handling capacity, resulting in intermittent delays.

Impact
During the incident, some automation requests took longer than expected to complete. No data loss occurred, and normal functionality was restored once the issue was resolved.

Resolution
Our engineering team investigated the issue and confirmed that the slowdown was related to higher‑than‑usual processing demand. We took immediate action to increase system capacity, which reduced processing delays and restored performance to normal levels. 

Prevention Measures
To reduce the likelihood of similar incidents in the future, we are taking the following steps:

  • Reviewing capacity thresholds for Associate Automation to better handle workload spikes
  • Improving monitoring and alerting on queue size and processing capacity
  • Evaluating autoscaling and deployment configurations to ensure scaling changes persist across deployments

We appreciate your patience and remain committed to providing a reliable and scalable service.

Posted Mar 06, 2026 - 09:30 GMT

Resolved

This incident has been resolved.
Posted Feb 25, 2026 - 14:15 GMT

Update

We are continuing to monitor for any further issues.
Posted Feb 25, 2026 - 12:47 GMT

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Feb 25, 2026 - 12:16 GMT

Update

We are continuing to work on a fix for this issue.
Posted Feb 25, 2026 - 11:51 GMT

Identified

The issue has been identified and a fix is being implemented.
Posted Feb 25, 2026 - 11:00 GMT

Investigating

We are currently experiencing slow performance issues on the platform which is also causing profiles to be stuck in "automating" for long periods of time.

Our engineers are investigating to resolve this issue as quickly as possible.
Posted Feb 25, 2026 - 10:19 GMT
This incident affected: Maxsight Environments (🇪🇺 EU - eu.maxsight.com).