Aderant Outage History

Aderant is up right now

Aderant had 18 outages in the last 2 years totaling 121h 26m of downtime — averaging 0.7 incidents per month.

There were 18 Aderant outages since October 9, 2025 totaling 121h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.aderant.com

Critical October 6, 2026

iTimekeep Connection Errors

Detected by Pingoru
Oct 06, 2026, 08:35 AM UTC
Resolved
Oct 06, 2026, 10:13 AM UTC
Duration
1h 37m
Affected: iTimekeep UK
Timeline · 3 updates
  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 →

Minor July 21, 2026

iTimekeep - Increased Latency

Detected by Pingoru
Jul 21, 2026, 03:07 PM UTC
Resolved
Jul 22, 2026, 01:26 AM UTC
Duration
10h 18m
Affected: iTimekeep US
Timeline · 7 updates
  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 →

Notice July 10, 2026

Conflicts Partial Outage – All Regions - New Search Creation Unavailable

Detected by Pingoru
Jul 10, 2026, 06:32 PM UTC
Resolved
Jul 12, 2026, 09:21 PM UTC
Duration
2d 2h
Affected: Conflicts USConflicts APAConflicts UKConflicts CANConflicts EU
Timeline · 4 updates
  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

    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.

Read the full incident report →

Major July 7, 2026

Onyx Canada - Unable to Login

Detected by Pingoru
Jul 07, 2026, 02:10 PM UTC
Resolved
Jul 07, 2026, 07:38 PM UTC
Duration
5h 27m
Affected: Onyx CAN
Timeline · 2 updates
  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 →

Major July 7, 2026

Onyx APA - Unable to LogIn

Detected by Pingoru
Jul 07, 2026, 01:40 PM UTC
Resolved
Jul 07, 2026, 03:04 PM UTC
Duration
1h 23m
Affected: Onyx APA
Timeline · 3 updates
  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 →

Notice June 9, 2026

Onyx Partial Outage - CAN, UK, APA, & EU

Detected by Pingoru
Jun 09, 2026, 06:36 PM UTC
Resolved
Jun 09, 2026, 06:43 PM UTC
Duration
6m
Affected: Onyx CANOnyx UKOnyx APAOnyx EU
Timeline · 2 updates
  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 →

Minor June 1, 2026

Intermittent iTimekeep Latency Issues

Detected by Pingoru
Jun 01, 2026, 03:57 PM UTC
Resolved
Jun 01, 2026, 04:47 PM UTC
Duration
50m
Affected: iTimekeep US
Timeline · 2 updates
  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 →

Notice May 4, 2026

Aderant Conflicts – Service Outage

Detected by Pingoru
May 04, 2026, 03:24 PM UTC
Resolved
May 04, 2026, 09:14 PM UTC
Duration
5h 49m
Affected: Conflicts USConflicts APAConflicts UKConflicts CANConflicts EU
Timeline · 5 updates
  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 →

Major April 29, 2026

Onyx Partial Outage

Detected by Pingoru
Apr 29, 2026, 09:26 PM UTC
Resolved
Apr 30, 2026, 01:14 AM UTC
Duration
3h 47m
Affected: Onyx USOnyx CANOnyx UKOnyx APAOnyx EU
Timeline · 2 updates
  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 →

Major March 30, 2026

BillBlast Partial Outage

Detected by Pingoru
Mar 30, 2026, 03:53 PM UTC
Resolved
Mar 30, 2026, 04:42 PM UTC
Duration
48m
Affected: BillBlast USBillBlast CANBillBlast UKBillBlast APA
Timeline · 2 updates
  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 →

Notice March 16, 2026

Aderant Cloud Conflicts - Partial Outage

Detected by Pingoru
Mar 16, 2026, 05:29 PM UTC
Resolved
Mar 17, 2026, 04:26 AM UTC
Duration
10h 57m
Affected: Conflicts CAN
Timeline · 3 updates
  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 →

Minor December 1, 2025

Intermittent iTimekeep Performance Issues

Detected by Pingoru
Dec 01, 2025, 03:39 PM UTC
Resolved
Dec 01, 2025, 06:42 PM UTC
Duration
3h 3m
Affected: iTimekeep US
Timeline · 3 updates
  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 →

Minor November 3, 2025

iTimekeep Intermittent Performance

Detected by Pingoru
Nov 03, 2025, 04:05 PM UTC
Resolved
Nov 03, 2025, 04:24 PM UTC
Duration
19m
Affected: iTimekeep US
Timeline · 3 updates
  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 →

Critical October 29, 2025

Microsoft Azure Service Interruption

Detected by Pingoru
Oct 29, 2025, 04:06 PM UTC
Resolved
Oct 30, 2025, 01:15 AM UTC
Duration
9h 9m
Affected: BillBlast USiTimekeep USOCG Live USThrive USConflicts USPassive Time Assistant – USOnyx USCloud AR USBillBlast CANiTimekeep CANOCG Live UKThrive CANConflicts APAPassive Time Assistant – APAOnyx CANBillBlast UKiTimekeep UKOCG Live EUThrive UKOnyx UKConflicts UKBillBlast APAiTimekeep EUThrive EUOnyx APAConflicts CANiTimekeep APAThrive APAConflicts EU
Timeline · 10 updates

Read the full incident report →

Notice October 21, 2025

Microsoft Azure Network Disruption – Monitoring iTimekeep Performance

Detected by Pingoru
Oct 21, 2025, 03:05 PM UTC
Resolved
Oct 21, 2025, 04:03 PM UTC
Duration
57m
Affected: iTimekeep US
Timeline · 2 updates
  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 →

Major October 20, 2025

Aderant Conflicts is experiencing

Detected by Pingoru
Oct 20, 2025, 08:54 PM UTC
Resolved
Oct 21, 2025, 01:44 AM UTC
Duration
4h 49m
Affected: Conflicts USConflicts CAN
Timeline · 5 updates
  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 →