Is Aderant down?

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.

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

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.

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.

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.

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.

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

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

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

We are continuing to investigate this issue.

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

Status: Resolved 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.

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.

This incident has been resolved.