Aderant Outage History

Started Oct 06, 2026, 08:35 AM UTC· resolved Oct 06, 2026, 10:13 AM UTC

1. investigating Oct 06, 2026, 08:35 AM UTC

   We are aware that iTimekeep users in the UK are experiencing errors, including difficulty loading timecards and connection errors. Our teams are actively investigating. Further updates will be posted here as they become available.

2. investigating Oct 06, 2026, 09:34 AM UTC

   Our cloud and development teams are continuing to investigate the errors affecting iTimekeep users in the UK, including difficulty loading timecards and connection errors. The cause has not yet been identified. Further updates will be posted here in an hour or as soon as they become available.

3. resolved Oct 06, 2026, 10:13 AM UTC

   Resolved - The errors affecting some iTimekeep users in the UK, including difficulty loading timecards and connection errors, have been resolved. The issue was traced to an unresponsive process on one of the servers supporting UK users, and a rolling restart of the affected service restored normal operation. We will continue to monitor closely.

Read the full incident report →

Started Jul 23, 2026, 05:01 PM UTC· resolved Jul 23, 2026, 09:06 PM UTC

1. investigating Jul 23, 2026, 05:01 PM UTC

   Microsoft has reported a networking issue affecting the Azure West US region, which is impacting some of our services. Per Microsoft, affected customers may experience intermittent connectivity failures, increased latency, or difficulty accessing services in that region. Microsoft has begun applying mitigations. We are engaged with them and monitoring closely. Further updates will be posted here, and Microsoft's status is available at https://azure.status.microsoft/en-us/status.

2. monitoring Jul 23, 2026, 05:16 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Jul 23, 2026, 06:02 PM UTC

   Correction to our previous update: the prior message associated with the status change to "Monitoring" was posted in error. No fix has been implemented, and this issue is not resolved. This is a Microsoft Azure networking issue in the West US region, which Microsoft has classified as critical. Resolution is on Microsoft's side and there is no corrective action available on our end. We are, however, in direct communication with the Microsoft team. Microsoft's mitigation attempts so far have not produced broad improvement, and no ETA is available. We will update as the situation changes. Microsoft's regional status is available at https://azure.status.microsoft/en-us/status.

4. monitoring Jul 23, 2026, 07:00 PM UTC

   Microsoft has identified a recent change strongly correlated with the onset of this issue and has begun rolling it back. That rollback is in progress, and early telemetry is showing signs of recovery. We are independently seeing improved performance and stability across affected services. This is not yet confirmed as resolved. Microsoft has not declared full recovery, and we are continuing to monitor closely alongside them until they do. We will update as the situation develops. Microsoft's regional status is available at https://azure.status.microsoft/en-us/status.

5. monitoring Jul 23, 2026, 08:10 PM UTC

   Performance across affected services has remained stable, and we are seeing close to normal operation. Microsoft's rollback of the correlated change appears to have taken effect. We are holding this in a monitoring state pending Microsoft's final resolution confirmation, and remain in contact with them. We will post a final update once Microsoft confirms full resolution. Microsoft's regional status is available at https://azure.status.microsoft/en-us/status.

6. resolved Jul 23, 2026, 09:06 PM UTC

   Microsoft has confirmed resolution of the Azure West US networking issue, and performance across all affected services has returned to normal and remained stable. We are considering this issue resolved. Thank you for your patience throughout. A root cause analysis from Microsoft is expected to follow, and we will share relevant detail once available. Microsoft's regional status is available at https://azure.status.microsoft/en-us/status.

Read the full incident report →

Started Jul 22, 2026, 01:52 PM UTC· resolved Jul 22, 2026, 09:00 PM UTC

1. investigating Jul 22, 2026, 01:52 PM UTC

   The performance degradation affecting iTimekeep yesterday persists and is being investigated further with Microsoft for resolution.

2. investigating Jul 22, 2026, 03:04 PM UTC

   Our teams are continuing to investigate the performance degradation, working alongside Microsoft toward resolution.

3. investigating Jul 22, 2026, 03:59 PM UTC

   Our teams remain engaged with Microsoft to address the latency. A subset of instances is experiencing higher than normal response times. Latency has stabilized and is running below yesterday's peak, though it remains elevated. Investigation continues and further updates will be posted here.

4. investigating Jul 22, 2026, 04:58 PM UTC

   Our teams remain engaged with Microsoft on the latency. Investigation continues on multiple fronts simultaneously. Root cause has not yet been identified. Performance remains stable but elevated above normal.

5. investigating Jul 22, 2026, 06:17 PM UTC

   Our teams remain engaged with Microsoft on the latency affecting iTimekeep. We are evaluating a potential resolution path and testing it before any broader application. Performance remains stable but elevated above normal.

6. investigating Jul 22, 2026, 07:24 PM UTC

   Our teams are continuing to test a potential resolution for the latency affecting iTimekeep. We will share more specific detail, including any planned maintenance, once we are able to. Performance remains stable but elevated above normal.

7. identified Jul 22, 2026, 07:45 PM UTC

   iTimekeep - Scheduled Outage We apologize for the continued disruption, and we appreciate your patience as we work to resolve it. We will be applying a change to improve the experience during a planned outage from 4:15 PM to 6:15 PM EDT. iTimekeep will be inaccessible during this time Please share this information with your timekeepers so they are aware iTimekeep will be unavailable during the timeframe below. Outage: iTimekeep will be inaccessible from 4:15 PM to 6:15 PM EDT. Impact: No customer impact or UI changes. No customer action is required. We recommend timekeepers save any in-progress work before 4:15 PM EDT. We will confirm here once service is restored.

8. identified Jul 22, 2026, 08:00 PM UTC

   iTimekeep - Scheduled Outage Please note a change in timeframe for the planned outage: We apologize for the continued disruption, and we appreciate your patience as we work to resolve it. We will be applying a change to improve the experience during a planned outage from 4:15 PM to 5:15 PM EDT. iTimekeep will be inaccessible during this time Please share this information with your timekeepers so they are aware iTimekeep will be unavailable during the timeframe below. Outage: iTimekeep will be inaccessible from 4:15 PM to 5:15 PM EDT. Impact: No customer impact or UI changes. No customer action is required. We recommend timekeepers save any in-progress work before 4:15 PM EDT. We will confirm here once service is restored.

9. resolved Jul 22, 2026, 09:00 PM UTC

   The maintenance work to address the latency affecting iTimekeep is complete, and iTimekeep is available for normal use. We are seeing improved performance and will continue to monitor closely to ensure it holds. A root cause analysis is ongoing and will be shared once complete. Thank you for your patience throughout.

Read the full incident report →

Started Jul 21, 2026, 03:07 PM UTC· resolved Jul 22, 2026, 01:26 AM UTC

1. investigating Jul 21, 2026, 03:07 PM UTC

   We are aware of increased latency affecting iTimekeep and some users may experience slower than normal response times. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will provide an update as soon as we have more information

2. investigating Jul 21, 2026, 04:21 PM UTC

   Our teams are continuing to actively investigate the increased latency affecting iTimekeep. You may continue to experience slower than normal response times while we work on this. We apologize for the continued inconvenience and will provide a further update as soon as we have more information.

3. investigating Jul 21, 2026, 06:27 PM UTC

   We are still working to resolve the performance issues affecting iTimekeep, and this remains our team's top priority. Response times are slower than normal, and some actions may fail and need to be retried. We are focused on restoring normal performance as quickly as we safely can.

4. investigating Jul 21, 2026, 08:33 PM UTC

   Our teams remain fully engaged on the performance issues affecting iTimekeep. This is our top priority and work is ongoing. What you may see: slower than normal response times, and in some cases an action may fail. If an action does not complete, we recommend avoiding repeated retries of the same action to minimize the risk of duplicate entries or other issues. We understand the impact this has on capturing your time and we are working to restore normal performance as quickly as we safely can.

5. identified Jul 21, 2026, 10:06 PM UTC

   Working closely with Microsoft, we have identified the source of the issue and a fix is now being implemented. We are actively monitoring progress and will continue to keep you updated as we move toward resolution. Thank you for your patience and partnership.

6. identified Jul 21, 2026, 11:59 PM UTC

   To address an underlying Microsoft issue, we will be taking an emergency outage tonight from 9:00 PM EDT / 6:00 PM PDT for approximately 15–20 minutes. During this time, iTimekeep will be inaccessible. Service will be restored immediately once the work is complete. We appreciate your patience and understanding as we work to resolve this issue as quickly as possible.

7. resolved Jul 22, 2026, 01:26 AM UTC

   We’re pleased to let you know that the incident has been resolved. Our team will continue to monitor the situation closely and will share any relevant updates if needed.

Read the full incident report →

Started Jul 10, 2026, 06:32 PM UTC· resolved Jul 12, 2026, 09:21 PM UTC

1. investigating Jul 10, 2026, 06:32 PM UTC

   We are currently investigating an issue preventing new searches from being created. Existing searches and previously created search results remain available. At this time, the impact appears limited to the creation of new searches only. Our team is actively investigating the cause and working to restore normal functionality as quickly as possible. We will provide an update as soon as more information is available. Thank you for your patience.

2. investigating Jul 10, 2026, 08:15 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 10, 2026, 08:16 PM UTC

   **Monitoring** - We have identified that the issue preventing new searches from being created appears to be related to continued impact from a previous LaunchDarkly incident affecting SDK and flag delivery evaluations. We have re-established the impacted connections and are monitoring the environment to confirm that new search creation remains stable. Customers may begin seeing recovery, though some intermittent impact may continue while monitoring is in progress. We will provide another update once stability has been confirmed.

4. resolved Jul 12, 2026, 09:21 PM UTC

   Summary: Conflict searches were failing due to a third-party service disruption (LaunchDarkly) that began on July 10, 2026. What happened: Our feature flag provider, LaunchDarkly, experienced a global service outage beginning at approximately 12:16 PM EDT on July 10. During this outage, their servers returned authentication errors (HTTP 401) to all connected applications. The LaunchDarkly server-side SDK used by the Conflicts search processing service entered a permanent error state and was unable to self-recover once LaunchDarkly restored service. Resolution: All affected application services were restarted across all regions, re-establishing connections to LaunchDarkly. Normal search operations were fully restored by approximately 8:00 PM EDT July 10. . No data was lost, any searches that failed during the incident can be re-run successfully.

Read the full incident report →

Started Jul 07, 2026, 02:10 PM UTC· resolved Jul 07, 2026, 07:38 PM UTC

1. investigating Jul 07, 2026, 02:10 PM UTC

   We are currently investigating an issue affecting Onyx in the Canada region. Users are currently unable to log in to the application. Our team is actively working to restore service as quickly as possible. Thank you for your patience.

2. resolved Jul 07, 2026, 07:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 01:40 PM UTC· resolved Jul 07, 2026, 03:04 PM UTC

1. investigating Jul 07, 2026, 01:40 PM UTC

   We are currently investigating an issue affecting Onyx in the APA region. Users are currently unable to log in to the application. Our team is actively working to restore service as quickly as possible. Thank you for your patience.

2. investigating Jul 07, 2026, 02:10 PM UTC

   We are continuing to investigate this issue.

3. resolved Jul 07, 2026, 03:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 09, 2026, 06:36 PM UTC· resolved Jun 09, 2026, 06:43 PM UTC

1. investigating Jun 09, 2026, 06:36 PM UTC

   We are currently experiencing an issue that is preventing users from logging into the Onyx web application in the CAN, UK, APA, and EU regions. Onyx US is functioning normally. Our team is actively investigating the problem. Onyx rule validations are functioning normally and generating alerts in other applications without any issues.

2. resolved Jun 09, 2026, 06:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 03:57 PM UTC· resolved Jun 01, 2026, 04:47 PM UTC

1. investigating Jun 01, 2026, 03:57 PM UTC

   We are currently investigating intermittent latency for some users.

2. resolved Jun 01, 2026, 04:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 04, 2026, 03:24 PM UTC· resolved May 04, 2026, 09:14 PM UTC

1. investigating May 04, 2026, 03:24 PM UTC

   We are currently investigating an issue affecting data currency in Aderant Conflicts. To prevent users from receiving potentially inaccurate or outdated search results, we have temporarily disabled access to the Aderant Conflicts web applications. Users are currently unable to access the web application or perform searches. Our team is actively investigating and will provide an update as soon as more information is available.

2. investigating May 04, 2026, 05:49 PM UTC

   We are continuing to investigate this issue.

3. identified May 04, 2026, 05:50 PM UTC

   The issue has been identified. Service has been restored in the UK, Canada, and EU regions, and the Aderant Conflicts web applications have been turned back on for those regions. We are continuing work to restore service in the remaining affected regions and will provide another update as more information becomes available.

4. identified May 04, 2026, 07:14 PM UTC

   The issue has been identified. Service has been restored in the APA, UK, Canada, and EU regions, and the Aderant Conflicts web applications have been turned back on for those regions. We are continuing work to restore service in the US region and will provide another update as more information becomes available.

5. resolved May 04, 2026, 09:14 PM UTC

   Aderant Conflicts – Service Restored All issues affecting Aderant Conflicts have been resolved. The web applications have been restored, and service is available in all regions. Users may resume normal use of the system. Thank you for your patience while we investigated and resolved this issue.

Read the full incident report →

Started Apr 29, 2026, 09:26 PM UTC· resolved Apr 30, 2026, 01:14 AM UTC

1. investigating Apr 29, 2026, 09:26 PM UTC

   We are currently experiencing an issue that is preventing users from logging into the Onyx web application. Our team is actively investigating the problem. Onyx Rules are functioning normally and generating alerts in other applications without any issues.

2. resolved Apr 30, 2026, 01:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 30, 2026, 03:53 PM UTC· resolved Mar 30, 2026, 04:42 PM UTC

1. investigating Mar 30, 2026, 03:53 PM UTC

   We have identified an issue impacting some BillBlast functionality. Our teams are investigating and will provide an update as soon as more information becomes available. In the meantime, you may experience unexpected "failure messages" or delays/interruptions in service. Please monitor the myAderant Support Portal or the Status Page for updates Thank you, BillBlast Suport Team

2. resolved Mar 30, 2026, 04:42 PM UTC

   The issue previously impacting some BillBlast functionality has now been resolved.

Read the full incident report →

Started Mar 16, 2026, 05:29 PM UTC· resolved Mar 17, 2026, 04:26 AM UTC

1. investigating Mar 16, 2026, 05:29 PM UTC

   We are currently experiencing a partial outage affecting Aderant Conflicts. Users may encounter errors when running searches due to an issue affecting search processing. Some searches may also fail during follow-up processing actions related to those searches. Our teams are actively investigating and working to restore full functionality. Additional updates will be shared as they become available. Thank you for your patience. Aderant

2. monitoring Mar 16, 2026, 10:19 PM UTC

   Update: We have identified that the earlier disruption affecting search functionality for customers hosted in the Canada Central region was related to an issue within the underlying Microsoft Azure infrastructure supporting the service. Microsoft has indicated that the issue has now been mitigated, and services are currently recovering. Our team is continuing to monitor system activity to confirm that search functionality has returned to normal and remains stable. We appreciate your patience while this issue was being addressed. Additional updates will be shared if necessary. Thank you, Aderant

3. resolved Mar 17, 2026, 04:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 01, 2025, 03:39 PM UTC· resolved Dec 01, 2025, 06:42 PM UTC

1. investigating Dec 01, 2025, 03:39 PM UTC

   We are currently investigating intermittent iTimekeep performance issues.

2. monitoring Dec 01, 2025, 04:54 PM UTC

   System logs, telemetry, and live checks show the environment running as expected and performing within normal thresholds. We continue to monitor the while our teams investigate root cause.

3. resolved Dec 01, 2025, 06:42 PM UTC

   Normal performance has been restored.

Read the full incident report →

Started Nov 03, 2025, 04:05 PM UTC· resolved Nov 03, 2025, 04:24 PM UTC

1. investigating Nov 03, 2025, 04:05 PM UTC

   We are currently monitoring an intermittent performance issue with iTimekeep performance. Our technical team is investigating the issue and working to restore normal service levels. We will provide updates as soon as more information becomes available. We apologize for any inconvenience. For the latest status updates, please visit: https://status.aderant.com/

2. monitoring Nov 03, 2025, 04:19 PM UTC

   iTimekeep performance has returned to expected levels. The underlying cause was investigated, and corrective measures were implemented. We believe the issue has been resolved based on the latest monitoring results and user reports. With this, we continue to monitor the situation closely to ensure stability and confirm that the resolution remains effective. We apologize for any inconvenience that you may have experienced.

3. resolved Nov 03, 2025, 04:24 PM UTC

   A single instance of iTimekeep saw a small period of elevated latency that presented as intermittent errors for a small subset of users. This latency has subsided and we are seeing normal performance across all instances.

Read the full incident report →

Started Oct 29, 2025, 04:06 PM UTC· resolved Oct 30, 2025, 01:15 AM UTC

1. investigating Oct 29, 2025, 04:06 PM UTC

   We are investigating a Microsoft Azure incident impacting multiple services. Our engineering team is actively working with Microsoft to identify the root cause and restore service.

2. investigating Oct 29, 2025, 04:28 PM UTC

   We are continuing to actively engage with Microsoft regarding the ongoing Azure incident impacting our services. We will continue to provide updates as new information becomes available. Thank you for your patience and understanding.

3. investigating Oct 29, 2025, 05:12 PM UTC

   Microsoft has reported an issue with Azure Front Door affecting access to some services and the Azure Portal. Microsoft has implemented mitigation steps and is continuing to assess recovery options. We remain in close communication with Microsoft. Further updates will be provided within 60 minutes or sooner.

4. identified Oct 29, 2025, 05:44 PM UTC

   Microsoft has indicated that an inadvertent configuration change may have triggered the incident. Microsoft has taken two key mitigation steps: • Blocking all configuration changes to AFD services • Rolling back to the last known good configuration state There is no confirmed ETA for completion of the rollback. Microsoft continues to work toward full restoration, and we will share another update as information becomes available.

5. identified Oct 29, 2025, 06:45 PM UTC

   We are continuing to closely monitor the ongoing Azure Front Door issue. Microsoft is actively working to resolve the underlying problem, and we remain in regular communication with their engineering teams. At this time, we are still awaiting the next update from Microsoft. We will share additional information as soon as it becomes available. Thank you for your continued patience and understanding.

6. identified Oct 29, 2025, 07:36 PM UTC

   Restoration in Progress Following our last update regarding the Azure Front Door (AFD) and DNS-related service disruption, we want to share the latest developments from Microsoft. Microsoft has confirmed that the issue stemmed from an unintended configuration change within AFD. In response, they initiated a rollback to the last known stable configuration and temporarily blocked all configuration changes to AFD services. As of now, Microsoft is actively working to restore full performance by recovering nodes and routing traffic through healthy infrastructure. As progress continues, service availability is expected to improve, though you may see intermittent errors until full recovery. Microsoft is anticipating full mitigation within the next four hours. https://azure.status.microsoft/en-us/status Our Cloud Operations team remains in close coordination with Microsoft and continues to monitor the impact on Aderant services. We understand how critical these services are to your operations and appreciate your continued patience. We will provide further updates as new information becomes available.

7. identified Oct 29, 2025, 08:46 PM UTC

   Following our previous update regarding the Azure Front Door (AFD) and DNS-related service disruption, we want to share the latest developments from Microsoft. Microsoft has now completed deployment of the “last known good” configuration. As a result, customers may have already begun to see signs of recovery. Microsoft continues to actively restore full performance. As this work progresses, service availability is expected to steadily improve anticipating full recovery by 7:20 PM EST on October 29, 2025. https://azure.status.microsoft/en-us/status Our Cloud Operations team remains in close coordination with Microsoft and continues to monitor the impact on Aderant services. We will provide additional updates as new information becomes available.

8. identified Oct 29, 2025, 11:11 PM UTC

   Following our previous update, Microsoft recovery efforts remain underway, with nodes being restored and traffic re-routed through healthy infrastructure. As recovery continues, some requests may still encounter intermittent failures or reduced availability. Microsoft is gradually reloading configurations and rebalancing traffic across a large number of nodes to restore full operational scale. This process is intentionally gradual to ensure stability and prevent overload as dependent services recover. Strong signs of improvement are being reported across affected regions. Microsoft remains on track for full mitigation by 7:20 PM EST on October 29, 2025, and will communicate if recovery is achieved sooner. 🔗 https://azure.status.microsoft/en-us/status Our Cloud Operations team continues to monitor the impact on Aderant services and remains in close coordination with Microsoft.

9. monitoring Oct 29, 2025, 11:43 PM UTC

   We are seeing improved performance across all affected applications globally as Microsoft continues their recovery efforts. While Microsoft continues to remediate nodes across all regions, we expect to see degraded performance while accessing applications including intermittent connection errors. Refreshing the application typically reroutes user traffic to a node that is functional. We are not anticipating any additional steps from end-users required for on-premise connector applications. Our team is continuing to monitor and will provide updates as we get them.

10. resolved Oct 30, 2025, 01:15 AM UTC

    Microsoft has confirmed that the Azure Front Door issue has been fully resolved, and all related services have stabilized. Aderant services are now functioning properly and operating sustainably. Microsoft is preparing a Root Cause Analysis (RCA), which we will share once it becomes available. Thank you for your patience and understanding throughout this incident.

Read the full incident report →

Started Oct 21, 2025, 03:05 PM UTC· resolved Oct 21, 2025, 04:03 PM UTC

1. monitoring Oct 21, 2025, 03:05 PM UTC

   Microsoft has reported a network disruption affecting portions of the Azure platform. This may cause intermittent connectivity or access issues when managing some Azure workloads. Microsoft is actively investigating and has observed early signs of recovery while continuing to apply mitigation steps to fully restore service. Our team is closely monitoring iTimekeep to ensure optimal performance and will continue to provide updates as the situation evolves or within the next 60 minutes, whichever comes first. Thank you for your patience and understanding.

2. resolved Oct 21, 2025, 04:03 PM UTC

   Microsoft has resolved the network disruption affecting portions of Azure. iTimekeep is operating normally.

Read the full incident report →

Started Oct 20, 2025, 08:54 PM UTC· resolved Oct 21, 2025, 01:44 AM UTC

1. investigating Oct 20, 2025, 08:54 PM UTC

   We are currently experiencing an outage with Aderant Conflicts. Conflicts searches are failing. Our team is investigating the outage. We will continue to provide regular updates as we work to restore full functionality.

2. investigating Oct 20, 2025, 09:58 PM UTC

   We are continuing to investigate this issue.

3. identified Oct 20, 2025, 11:46 PM UTC

   It was identified that the issue originated from a recent change implemented by Microsoft Azure, which temporarily disrupted key integrations that Conflicts application depends on. Our Cloud Operations team is actively performing a resynchronization and validation process to restore full functionality. Initial testing indicates that this approach is addressing the core issue, and we are working to complete verification before bringing all services back online.

4. investigating Oct 21, 2025, 12:10 AM UTC

   We are currently investigating this issue.

5. resolved Oct 21, 2025, 01:44 AM UTC

   The incident has been resolved, and Conflicts is now available. Please note that initial searches may experience a delay of up to 45 minutes. This should resolve automatically without any action required. Once a search completes successfully, subsequent searches are expected to perform normally. If a search remains unresponsive for more than an hour, please contact Aderant Support for further investigation. Thank you for your patience and cooperation.

Read the full incident report →

Started Oct 01, 2025, 07:20 PM UTC· resolved Oct 02, 2025, 09:35 PM UTC

1. 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.

2. investigating Oct 01, 2025, 08:30 PM UTC

   We are continuing to investigate this issue.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

Read the full incident report →

Started Sep 19, 2025, 12:43 PM UTC· resolved Sep 19, 2025, 05:23 PM UTC

1. identified Sep 19, 2025, 12:43 PM UTC

   Our team continues to actively investigate the issue, and based on our findings, we have also engaged Microsoft to assist with resolving an underlying Azure resource problem. At this time, we do not yet have an estimated timeframe for resolution. Please rest assured that we are working with urgency and will continue to keep you informed as progress is made. We sincerely appreciate your patience and understanding while we work to restore full service.

2. identified Sep 19, 2025, 01:48 PM UTC

   We continue to work closely with Microsoft to address the underlying issue. Their specialists are actively engaged alongside our team to expedite resolution. At this time, service remains unavailable and we are still unable to provide a confirmed resolution timeframe. We understand the impact this may have on your operations, and please be assured that restoring full service remains our highest priority. We will continue to share updates as new information becomes available. Thank you for your continued patience and understanding.

3. identified Sep 19, 2025, 03:35 PM UTC

   As of 10:55 AM, it has been confirmed that the underlying issue is within Microsoft Azure and impacting iTimekeep services. We are actively engaged with Microsoft as they work toward resolution and will continue to provide updates as more information becomes available. At this time, service remains unavailable and we are still unable to provide a confirmed resolution timeframe. We understand the impact this may have on your operations, and please be assured that restoring full service remains our highest priority. We will continue to share updates as new information becomes available. Thank you for your continued patience and understanding.

4. identified Sep 19, 2025, 04:34 PM UTC

   We are still awaiting Microsoft’s action to address the underlying issue causing the iTimekeep service disruption. We remain fully engaged with their team and will continue to provide updates as new information becomes available.

5. resolved Sep 19, 2025, 05:23 PM UTC

   We are pleased to inform you that Microsoft has confirmed the underlying issue has been addressed on their side, and Aderant can confirm that iTimekeep service has been restored. As part of this process, impacted clients may need to restart iTimekeep Connect. If you have any questions or encounter further issues, please contact Aderant Support for assistance. Additionally, a Root Cause Analysis (RCA) will be shared once we receive the official RCA from Microsoft and can incorporate it into our communication.

Read the full incident report →

Started Sep 03, 2025, 02:45 PM UTC· resolved Sep 03, 2025, 04:00 PM UTC

1. investigating Sep 03, 2025, 02:45 PM UTC

   As iTimekeep is experiencing an issue in the US, Onyx access is currently unavailable at this region. New logins cannot be completed; however, users who were logged in before the issue began can still access the system.

2. resolved Sep 03, 2025, 04:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 03, 2025, 01:47 PM UTC· resolved Sep 04, 2025, 02:27 PM UTC

1. investigating Sep 03, 2025, 01:47 PM UTC

   We are investigating an issue affecting the iTimekeep experience in the US region.

2. investigating Sep 03, 2025, 01:48 PM UTC

   We are investigating an issue affecting the iTimekeep experience in the US region.

3. investigating Sep 03, 2025, 02:59 PM UTC

   Our teams are actively implementing remediation steps to restore normal performance. This includes work on core system services to stabilize the environment and improve responsiveness. We will continue to share updates as progress is made.

4. monitoring Sep 03, 2025, 03:46 PM UTC

   Our team is seeing improved performance and are working with customers on confirmation and any needed remediation steps. We are continuing to monitor the situation and will share updates as they become available.

5. monitoring Sep 03, 2025, 04:22 PM UTC

   We are preparing to deploy an update to improve stability and system reliability. This change will be seamless to users, with no downtime required. Our team will closely monitor the deployment to ensure success and will provide confirmation once it is complete.

6. monitoring Sep 03, 2025, 04:35 PM UTC

   The stability update for iTimekeep has been successfully deployed. Our team is closely monitoring the system to confirm expected performance and quickly address any issues that may arise.

7. monitoring Sep 03, 2025, 06:46 PM UTC

   After closely monitoring system performance, we have stabilized the user experience and restored iTimekeep to expected performance levels. We will continue to monitor to ensure ongoing stability.

8. monitoring Sep 03, 2025, 07:53 PM UTC

   Our monitoring continues to confirm that iTimekeep is stable and operating at expected performance levels. We will maintain active monitoring to ensure the experience remains consistent.

9. monitoring Sep 03, 2025, 08:49 PM UTC

   Our monitoring continues to confirm that iTimekeep is stable and operating at expected performance levels. We will maintain active monitoring to ensure the experience remains consistent.

10. monitoring Sep 04, 2025, 12:38 AM UTC

    Our monitoring continues to confirm that iTimekeep is stable and operating at expected performance levels. We will continue monitoring overnight and tomorrow morning to ensure the experience remains consistent.

11. resolved Sep 04, 2025, 02:27 PM UTC

    We are closing this incident as monitoring confirms that iTimekeep remains stable and is performing as expected. Ensuring the reliability of our service remains our top priority. Thank you for your patience while we worked to restore service.

Read the full incident report →

Started Sep 02, 2025, 02:35 PM UTC· resolved Sep 03, 2025, 12:19 AM UTC

1. investigating Sep 02, 2025, 02:35 PM UTC

   Onyx login is currently intermittent due to an issue affecting access to the iTimekeep application in the US region.

2. investigating Sep 02, 2025, 09:00 PM UTC

   As iTimekeep continues working to resolve the authentication error, Onyx access remains unavailable. New logins cannot be completed; however, users who were logged in before the issue began can still access the system. Efforts are ongoing, and we will provide the next update once key progress milestones are reached.

3. resolved Sep 03, 2025, 12:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2025, 01:49 PM UTC· resolved Sep 03, 2025, 12:10 AM UTC

1. investigating Sep 02, 2025, 01:49 PM UTC

   We are currently investigating an issue that is affecting logins to the iTimekeep application in the US region.

2. investigating Sep 02, 2025, 01:59 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 02, 2025, 02:12 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Sep 02, 2025, 02:29 PM UTC

   We continue to monitor and actively address issues as they arise.

5. monitoring Sep 02, 2025, 03:13 PM UTC

   We are actively resolving an issue affecting logins to the iTimekeep application in the US region.

6. monitoring Sep 02, 2025, 03:51 PM UTC

   We have identified the likely cause of the degraded performance in iTimekeep. Our investigation indicates that the issue is related to cache population. Our CloudOps team is actively implementing a solution. Once this solution is in place, we will provide a further update on progress and resolution. Thank you for your patience as we work to restore full performance as quickly as possible.

7. monitoring Sep 02, 2025, 04:50 PM UTC

   Our team continues to work on addressing the cache population. Efforts remain ongoing, and we will provide the next update once progress milestones are reached.

8. monitoring Sep 02, 2025, 06:22 PM UTC

   The fix is being verified to ensure stability and effectiveness before we apply it to the production environment. We will provide a further update once the rollout begins.

9. monitoring Sep 02, 2025, 07:13 PM UTC

   The fix has been successfully verified and is now being applied to the production environment. We are monitoring the results. There will be no downtime as part of applying the fix to the production environment.

10. monitoring Sep 02, 2025, 08:16 PM UTC

    We are in the process of applying the fix to production. We continue to actively monitor the changes to confirm effectiveness and determine if any further efforts are required.

11. monitoring Sep 02, 2025, 11:06 PM UTC

    We continue to monitor changes made to confirm effectiveness and determine if any further efforts are required.

12. resolved Sep 03, 2025, 12:10 AM UTC

    The fix mentioned previously has been implemented in Production. Indications are that the incident has been resolved and iTimekeep performance has been restored. If you are still experiencing any degraded performance, please restart iTimekeep Connect. Should issues persist after a restart, contact Aderant Support for further assistance.

Read the full incident report →

Started Jul 31, 2025, 02:05 PM UTC· resolved Jul 31, 2025, 02:10 PM UTC

1. identified Jul 31, 2025, 02:05 PM UTC

   We are currently experiencing an outage with Aderant Identity, which is preventing users from logging into products that rely on this service. Our team has pinpointed the root cause and is actively implementing a fix. We will continue to provide regular updates as we work to restore full functionality. Thank you for your patience.

2. resolved Jul 31, 2025, 02:10 PM UTC

   The Aderant Identity service is now fully operational. A fix has been implemented and we are actively monitoring the results.

Read the full incident report →