Abrigo ID
Timeline · 5 updates
- investigating Sep 21, 2026, 04:01 PM UTC
We are currently investigating an issue where customers are unable to log in through Abrigo ID to multiple products. As soon as we have more information an update will be added.
- monitoring Sep 21, 2026, 04:48 PM UTC
A fix has been implemented and we are monitoring until we can deploy an update. The team will continue to monitor login capability and address any issues that may arise immediately. We do expected a few customers to see degraded performance when logging in as we identify the permanent fix.
- monitoring Sep 22, 2026, 05:05 PM UTC
Within the Sageworks Analyst suite beginning 9/21, some users have experienced intermittent issues with left-hand navigation loading, general latency, and Abrigo ID login failures. Abrigo engineering and network teams are actively investigating the underlying cause and have implemented infrastructure adjustments to improve stability while that investigation continues. We are closely monitoring system performance and have seen improved stability as of 11:15 AM ET 9/22. Monitoring, identifying and addressing the underlying cause remains a high priority. We understand the disruption this may cause and will continue to provide updates as we learn more.
- monitoring Sep 22, 2026, 09:49 PM UTC
Updates Postponed The updates made to the Lending and Portfolio Risk solutions over the weekend are going to be temporarily rolled back today, September 22 at 8:00pm ET, and re-released at a future date. We will communicate timing as soon as it's available. We apologize for any latency you may have experienced this week and look forward to making the enhancements available as soon as possible. As a reminder, you can see the enhancement list through the Abrigo Community.
- resolved Sep 23, 2026, 04:23 PM UTC
Reverting to the August release was successful and all issues related to the September release have been resolved. Once the root cause has been identified and resolved communications will be sent for the next release using the normal notification path.