Aderant experienced a minor incident on October 1, 2025 affecting iTimekeep US, lasting 1d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2025, 07:20 PM UTC
We are currently investigating reports of sub-optimal performance in iTimekeep. We will provide updates here as more information becomes available.
- investigating Oct 01, 2025, 08:30 PM UTC
We are continuing to investigate this issue.
- investigating Oct 01, 2025, 09:18 PM UTC
Our team has identified a potential issue within the code that may be contributing to the performance challenges some clients have reported. We are actively addressing this finding and continuing to investigate to determine if it is the root cause. Please be assured that our engineers are treating this with the highest priority, and we are committed to restoring optimal performance. We will share further updates as soon as they are available. Thank you for your continued patience and trust as we work diligently toward a resolution.
- investigating Oct 01, 2025, 10:32 PM UTC
Our team continues to actively address the code finding we identified and is conducting a thorough investigation to determine whether this is the root cause of the reported performance issues. Resolving this matter remains our highest priority, and our engineers are working diligently to ensure iTimekeep performs at the level you expect. We will provide additional updates as our investigation progresses. Thank you for your patience and trust as we work toward a full resolution.
- investigating Oct 01, 2025, 11:40 PM UTC
Our team continues to address the issue and investigate the root cause of the performance concerns reported. This remains our highest priority, and we are committed to resolving the matter as quickly as possible. Further updates will be shared as progress is made. Thank you for your continued patience and trust.
- investigating Oct 02, 2025, 12:58 AM UTC
Our team continues to work diligently to address the performance issue. Resolving this remains our top priority, and we will share further updates as progress is made. Thank you for your patience and understanding.
- investigating Oct 02, 2025, 11:48 AM UTC
We are in the process of deploying a code change designed to address the reported performance issues. This change will be in production shortly. Once deployed, our team will closely monitor iTimekeep’s performance to ensure stability and confirm that no further changes are needed to return the system to expected performance levels. Thank you for your patience and trust as we work to fully resolve this matter.
- investigating Oct 02, 2025, 12:37 PM UTC
Our team is making additional changes to further address iTimekeep performance. These updates are intended to strengthen stability and ensure the system returns to the expected performance levels. We remain fully committed to resolving this matter and will continue to provide updates as progress is made. Thank you for your patience and trust as we work diligently toward resolution.
- investigating Oct 02, 2025, 01:07 PM UTC
We are pushing a change to production intended to improve system performance. Once this change is live, our teams will closely monitor iTimekeep to ensure performance returns to expected levels and remains stable. We appreciate your patience and continued trust as we work to resolve this matter fully.
- investigating Oct 02, 2025, 02:55 PM UTC
We continue to closely monitor iTimekeep to validate that performance has returned to expected levels. We appreciate your patience and continued trust as we work to fully resolve this matter.
- investigating Oct 02, 2025, 05:11 PM UTC
We continue to closely monitor iTimekeep following the performance issues that began yesterday afternoon. While iTimekeep remains available, we are keeping the incident open as we track performance metrics and user experience throughout the day. Our engineering team remains actively engaged, and we will provide an update if conditions change or as soon as additional information is available. Thank you for your patience and trust as we ensure the stability of the service.
- resolved Oct 02, 2025, 09:35 PM UTC
The incident has been resolved and iTimekeep is operating within expected performance parameters. A detailed Root Cause Analysis will be made available soon. We will continue to monitor the environment and pursue additional improvements to enhance the resilience and stability of the system. If you observe any residual issues or behavior inconsistent with normal operation, please contact us immediately. Thank you for your patience and cooperation.