- Detected by Pingoru
- Dec 19, 2026, 04:00 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- —
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Jan 28, 2026, 06:56 PM UTC
THIS IS A SCHEDULED EVENT Dec 19 , 10:00 - 18:00 CST Jan 28 , 12:56 CST Scheduled - "Tracker will be undergoing maintenance and unavailable on Saturday 12/19/2026, from 9:00 AM PST to 5:00 PM PST."
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 04:22 PM UTC
- Resolved
- Apr 29, 2026, 06:09 PM UTC
- Duration
- 1h 46m
Affected: CLEARWestlaw US
Timeline · 2 updates
-
investigating Apr 29, 2026, 04:22 PM UTC
We are currently experiencing a performance issue with Searches with our CLEAR and Public Records applications. Our team is actively working to resolve this matter as quickly as possible. We apologize for any inconvenience and appreciate your understanding and patience.
-
resolved Apr 29, 2026, 06:09 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 11:53 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 1d 18h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 25, 2026, 11:53 PM UTC
Apr 25 , 18:53 CDT Resolved - This incident has been resolved. Apr 25 , 18:35 CDT Update - A fix has been implemented, and we are monitoring the results. Apr 25 , 18:33 CDT Update - We are continuing to investigate this issue. Apr 25 , 18:04 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 02:59 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 5d 15h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 22, 2026, 02:59 AM UTC
Apr 21 , 21:59 CDT Resolved - This incident has been resolved. Apr 21 , 18:57 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 12:10 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 15d 17h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 12, 2026, 12:10 AM UTC
Apr 11 , 19:10 CDT Resolved - This incident has been resolved. Apr 11 , 16:47 CDT Monitoring - Systems are online. We are monitoring performance and error rates. Apr 11 , 13:47 CDT Update - The primary fix has been implemented and systems are coming back online. Apr 11 , 11:01 CDT Identified - The issue has been identified and a fix is being implemented. Apr 11 , 09:11 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 01:33 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 20d 4h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 07, 2026, 01:33 PM UTC
Apr 7 , 08:33 CDT Resolved - This incident has been resolved. Apr 7 , 08:33 CDT Update - Our provider has resolved the connectivity issue impacting our UK datacentre, and all services are now operational. Root cause details are not yet available. We will provide further information if required. This incident is now closed. Apr 7 , 08:14 CDT Update - We are actively working with the provider to resolve the UK datacentre connectivity issue. While there is no new update at this time, we will share further information as soon as possible. Apr 7 , 07:44 CDT Investigating - One of our UK datacentres is currently inaccessible and we are actively engaging with the provider. All customers hosted at this location are impacted.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 03:25 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 24d 14h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 03, 2026, 03:25 AM UTC
Apr 2 , 22:25 CDT Resolved - This incident has been resolved. Apr 2 , 18:35 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 10:20 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 26d 7h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 01, 2026, 10:20 AM UTC
Apr 1 , 05:20 CDT Resolved - The issue has been resolved, and outbound emails are now being sent successfully from the queue. Apr 1 , 05:11 CDT Identified - The issue has been identified and a fix is being implemented. Apr 1 , 04:51 CDT Update - We are currently investigating the issue. Apr 1 , 03:39 CDT Investigating - Outgoing emails are currently stuck in the queue, and the issue is under investigation.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 07:21 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 26d 10h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Apr 01, 2026, 07:21 AM UTC
Apr 1 , 02:21 CDT Resolved - This incident has been resolved. Apr 1 , 02:17 CDT Update - We are continuing to investigate this issue. Mar 31 , 17:33 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 05:03 AM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 27d 13h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Mar 31, 2026, 05:03 AM UTC
Mar 31 , 00:03 CDT Resolved - AI assisted research features are now operational Mar 30 , 19:28 CDT Investigating - We are currently conducting several updates which may result in service downtime for AI assisted research features. We expect systems will be restored shortly - thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 04:07 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 28d 2h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Mar 30, 2026, 04:07 PM UTC
Mar 30 , 11:07 CDT Resolved - The issue affecting access to Dashboards has been resolved. Service has been restored and customers should now be able to access Dashboards as normal. Mar 30 , 10:30 CDT Update - We are continuing to investigate this issue. Mar 30 , 09:01 CDT Investigating - Some customers hosted in the USA and UK regions are experiencing unavailability of Dashboards in HighQ. This is under investigation by the operations team.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 12:47 PM UTC
- Resolved
- Mar 30, 2026, 12:47 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 30, 2026, 12:47 PM UTC
Mar 30 , 07:47 CDT Resolved - The slowness reported earlier has been successfully addressed through a SKU upgrade, and the issue is now resolved. Services have stabilized and should now be functioning normally as expected. Mar 30 , 07:27 CDT Monitoring - A fix has been implemented and we are monitoring the results. Mar 30 , 07:24 CDT Update - The emergency maintenance has been completed successfully. Mar 30 , 06:33 CDT Update - The maintenance window starts now. Mar 30 , 05:20 CDT Investigating - An emergency maintenance activity has been scheduled in the Azure UK region and is expected to take approximately 30 minutes. During this maintenance window, end users may experience a brief service interruption or temporary outage. We apologize for any inconvenience this may cause and appreciate your patience and understanding. We will share an update once the confirmed start time is available.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 04:02 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 33d 2h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Mar 25, 2026, 06:29 PM UTC
Mar 25 , 11:02 CDT Resolved - This incident has been resolved. Mar 25 , 09:05 CDT Investigating - We are currently investigating the issue
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 01:25 PM UTC
- Resolved
- Apr 27, 2026, 06:09 PM UTC
- Duration
- 35d 4h
Affected: Thomson Reuters Legal Status service
Timeline · 1 update
-
investigating Mar 23, 2026, 01:25 PM UTC
Mar 23 , 08:25 CDT Resolved - This incident has been resolved. Mar 23 , 08:20 CDT Monitoring - Service has been restored for customers hosted in the Australia region. All backend services are now operational. We are actively monitoring the platform to ensure continued stability and are investigating the root cause of the issue. Further updates will be shared if required. Mar 23 , 07:25 CDT Investigating - We are currently investigating a service disruption affecting some customers hosted in the Australia region. Some backend services are unavailable, which may result in errors or inability to access the service. Our teams are actively working to restore normal operations and we will provide further updates as progress is made.
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2026, 01:45 AM UTC
- Resolved
- Mar 21, 2026, 01:45 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 21, 2026, 01:45 AM UTC
Mar 20 , 20:45 CDT Resolved - This incident has been resolved. Mar 20 , 19:45 CDT Update - We are continuing to investigate this issue. Mar 20 , 19:43 CDT Investigating - We are currently investigating this issue.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 12:30 AM UTC
- Resolved
- Mar 19, 2026, 12:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 20, 2026, 08:38 PM UTC
On Mar 19 between 12:26AM GMT and 10:59AM GMT we performed an emergency change for a production issue, which resulted in unplanned impact on the Files Module functionality for HighQ US and UK regions. The issue is fully mitigated
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 10:53 AM UTC
- Resolved
- Mar 18, 2026, 11:51 AM UTC
- Duration
- 57m
Affected: UK HiqhQ (Collaborate)
Timeline · 5 updates
-
investigating Mar 18, 2026, 10:53 AM UTC
We are currently investigating this issue.
-
investigating Mar 18, 2026, 11:04 AM UTC
We are investigating an extended service disruption related to a backend database issue. Automated recovery did not complete successfully, and our engineers are actively performing manual steps to restore service.
-
investigating Mar 18, 2026, 11:15 AM UTC
This issue continues to affect a subset of customers hosted in the UK. Our engineers remain actively engaged in manual recovery, which is taking additional time to complete safely. Further updates will be shared as work progresses.
-
investigating Mar 18, 2026, 11:50 AM UTC
The incident has been mitigated and service has been restored for affected customers. We are continuing to monitor the environment to ensure stability. A root cause investigation is now underway, and we will share further details once available.
-
resolved Mar 18, 2026, 11:51 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 12:06 PM UTC
- Resolved
- Mar 11, 2026, 02:38 PM UTC
- Duration
- 2h 32m
Affected: UK HiqhQ (Collaborate)
Timeline · 4 updates
-
investigating Mar 11, 2026, 12:06 PM UTC
The instance load time is unusually slow. The support team is currently investigating the issue.
-
investigating Mar 11, 2026, 12:07 PM UTC
We are continuing to investigate this issue.
-
identified Mar 11, 2026, 12:54 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 11, 2026, 02:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 03:59 PM UTC
- Resolved
- Mar 10, 2026, 08:30 PM UTC
- Duration
- 4h 30m
Affected: CoCounsel Core
Timeline · 2 updates
-
investigating Mar 10, 2026, 03:59 PM UTC
We are currently investigating the issue.
-
resolved Mar 10, 2026, 08:30 PM UTC
The issue has been fully mitigated; services are back to normal performance.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 10:51 AM UTC
- Resolved
- Mar 06, 2026, 02:57 PM UTC
- Duration
- 4h 5m
Affected: UK HiqhQ (Collaborate)
Timeline · 3 updates
-
investigating Mar 06, 2026, 10:51 AM UTC
HighQ UK support teams noticed 500 errors in DataDog relating to iSheets microservices on SG2 server hosted instances. When clients are attemtping to save their changes in iSheets, they receive the following error - "Due to a system error, this record has not been saved". Support groups have been engaged and are investigating the issue.
-
identified Mar 06, 2026, 11:42 AM UTC
The teams have discovered that the impacted iSheet database is in a recovery state, which is resulting in application errors when users attempt to save iSheets records. Engineering, Database and Platform teams are engaged and are working to restore the service. More information will be shared in subsequent communications.
-
resolved Mar 06, 2026, 02:57 PM UTC
The issue is resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 05:34 PM UTC
- Resolved
- Feb 27, 2026, 06:39 PM UTC
- Duration
- 1h 4m
Affected: CLEARCoCounsel CoreWestlaw US
Timeline · 3 updates
-
investigating Feb 27, 2026, 05:34 PM UTC
We are currently investigating this issue.
-
monitoring Feb 27, 2026, 06:21 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 27, 2026, 06:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 07:52 PM UTC
- Resolved
- Feb 26, 2026, 09:20 PM UTC
- Duration
- 1h 28m
Affected: CoCounsel CoreWestlaw US
Timeline · 3 updates
-
investigating Feb 26, 2026, 07:52 PM UTC
We are currently investigating this issue.
-
monitoring Feb 26, 2026, 08:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 26, 2026, 09:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 11:03 PM UTC
- Resolved
- Feb 25, 2026, 11:58 PM UTC
- Duration
- 55m
Affected: CoCounsel CoreWestlaw US
Timeline · 2 updates
-
investigating Feb 25, 2026, 11:03 PM UTC
We are currently investigating this issue.
-
resolved Feb 25, 2026, 11:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 07:28 PM UTC
- Resolved
- Feb 24, 2026, 12:19 PM UTC
- Duration
- 16h 50m
Affected: CoCounsel CoreWestlaw US
Timeline · 3 updates
-
investigating Feb 23, 2026, 07:28 PM UTC
We are currently investigating this issue.
-
monitoring Feb 23, 2026, 07:53 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 24, 2026, 12:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 05:12 PM UTC
- Resolved
- Feb 20, 2026, 09:46 PM UTC
- Duration
- 4h 34m
Affected: CoCounsel Core
Timeline · 2 updates
-
investigating Feb 20, 2026, 05:12 PM UTC
We are currently experiencing intermittent issues with the AI Research feature with our CoCounsel service. Our team is actively working to resolve this matter as quickly as possible. We apologize for any inconvenience and appreciate your understanding and patience. Further updates will be provided here as soon as we have more information. If you have any questions, please contact Customer Support.
-
resolved Feb 20, 2026, 09:46 PM UTC
This incident has been resolved.
Read the full incident report →