Verisk Outage History

Started Oct 19, 2026, 05:13 PM UTC· resolved Oct 19, 2026, 09:40 PM UTC

1. investigating Oct 19, 2026, 05:13 PM UTC

   We're actively investigating the ClaimSearch SSO login issue and XML failures to reach Claimsearch endpoints disruption and appreciate your patience as we work to identify the root cause.

2. investigating Oct 19, 2026, 06:25 PM UTC

   Our technical teams are actively investigating the ClaimSearch login issue and working toward resolution. We will provide further updates as more information becomes available.

3. identified Oct 19, 2026, 08:25 PM UTC

   Our technical teams have identified a connectivity issue with the Web Application Firewall. They are actively troubleshooting the issue with the WAF vendor to resolve it. The teams are working toward a resolution and will provide further updates as more information becomes available.

4. monitoring Oct 19, 2026, 09:26 PM UTC

   ClaimSearch website login has been restored following remediation actions conducted in coordination with our web application firewall provider. Our technical teams are continuing to monitor application availability and verify that access remains consistent and reliable.

5. monitoring Oct 19, 2026, 09:26 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Oct 19, 2026, 09:40 PM UTC

   ClaimSearch SSO login issue has been fully restored. We appreciate your patience during this time.

Read the full incident report →

Started Oct 06, 2026, 02:18 PM UTC· resolved Oct 06, 2026, 04:50 PM UTC

1. monitoring Oct 06, 2026, 02:18 PM UTC

   The data issue is resolved and monitoring the recovery activities. ETA - Two an half hours.

2. resolved Oct 06, 2026, 04:50 PM UTC

   Access for all users has been restored

Read the full incident report →

Started Oct 06, 2026, 01:31 PM UTC· resolved Oct 06, 2026, 01:31 PM UTC

1. resolved Oct 06, 2026, 01:31 PM UTC

   From September 22 through October 1, an issue prevented Claims Inquiry address searches from displaying property claim results that matched the Location of Loss. The issue has been resolved. If you performed address searches in Claims Inquiry during this period and want to confirm that no Location of Loss matching results were missed, please rerun those searches.

Read the full incident report →

Started Sep 28, 2026, 01:57 PM UTC· resolved Sep 28, 2026, 07:15 PM UTC

1. investigating Sep 28, 2026, 01:57 PM UTC

   We are investigating an issue where ClaimSearch FTP Match and Error files have not been generated since September 26. Our teams are actively investigating and working to restore normal file processing. We will provide further updates as they become available.

2. investigating Sep 28, 2026, 06:28 PM UTC

   We are continuing to process remaining files from 09/26 and 09/27 at this time.

3. resolved Sep 28, 2026, 07:15 PM UTC

   All missing ClaimSearch Match and Error files received through FTP have now been successfully processed. The issue is fully resolved, and normal file processing has resumed. Thank you for your patience and understanding while our teams worked to resolve this issue.

Read the full incident report →

Started Sep 25, 2026, 02:40 PM UTC· resolved Sep 26, 2026, 01:42 PM UTC

1. monitoring Sep 25, 2026, 02:40 PM UTC

   ClaimSearch Insights experienced a brief outage overnight, which was resolved this morning. As a result, some Live-boards may show data up to two days behind. We expect all data to be fully up in the next two hours. We apologise for the inconvenience and appreciate your patience

2. monitoring Sep 25, 2026, 04:18 PM UTC

   The data restoration process is still in progress. We expect all data to be fully available in ClaimSearch Insights by tomorrow morning. We sincerely regret the disruption and appreciate your patience as we work to complete the restoration.

3. monitoring Sep 26, 2026, 01:37 PM UTC

   The data restoration is complete. All data is now available in ClaimSearch Insights, and the affected dashboards and Liveboards are working as expected. Thank you for your patience.

4. resolved Sep 26, 2026, 01:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 12:37 PM UTC· resolved Sep 24, 2026, 01:09 PM UTC

1. investigating Sep 24, 2026, 12:30 PM UTC

   We're actively investigating the ClaimSearch login disruption and appreciate your patience as we work to identify the root cause.

2. monitoring Sep 24, 2026, 12:37 PM UTC

   Our technical teams identified the cause of the issue and determined that it was related to a recent change. The team rolled back the change to restore the affected services and resolve the issue. We're diligently overseeing system stability following the ClaimSearch Login to prevent any recurrence.

3. resolved Sep 24, 2026, 01:09 PM UTC

   Service has been fully restored for ClaimSearch login. We appreciate your patience during this time.

Read the full incident report →

Started Sep 14, 2026, 01:54 PM UTC· resolved Sep 14, 2026, 04:54 PM UTC

1. investigating Sep 14, 2026, 01:54 PM UTC

   Verisk Tech Teams are actively working on to reload the missing data

2. identified Sep 14, 2026, 02:57 PM UTC

   The data has been updated for the Claim Scoring and AF1 Government Liveboards. The technical teams are currently loading the required data to resolve access issues affecting the COM Dashboard and UF Errors. Thank you for your patience.

3. identified Sep 14, 2026, 04:09 PM UTC

   The data load to resolve the access issues is approximately 75% complete. Our technical teams are closely monitoring progress and working to restore access for all affected users.

4. resolved Sep 14, 2026, 04:54 PM UTC

   The data load has been successfully completed, and all previously reported access issues have been resolved. The technical teams have verified that the affected dashboards and liveboards are accessible and functioning as expected. Thank you for your patience while we worked to restore full access.

Read the full incident report →

Started Sep 03, 2026, 02:07 PM UTC· resolved Sep 03, 2026, 09:41 PM UTC

1. identified Sep 03, 2026, 02:07 PM UTC

   We are working to restore NCIC discrepancies in ClaimSearch, our team is fully engaged in resolving the issue.

2. identified Sep 03, 2026, 03:19 PM UTC

   Our teams are continuing to restore NCIC discrepancies in ClaimSearch. We appreciate your patience while we continue to resolve the issue.

3. identified Sep 03, 2026, 04:43 PM UTC

   Developers are currently working to correct the status mismatch from 9/1 and 9/2. We appreciate your patience as we work to resolve this issue.

4. identified Sep 03, 2026, 06:16 PM UTC

   Developers are currently working through updating the status. Once it is complete, another sync will be completed to update. The current Estimated Time for completion is 3-4 hours

5. identified Sep 03, 2026, 07:22 PM UTC

   Developers are currently still running the process to update the status. The ETA remains 2-3 hours at this time.

6. identified Sep 03, 2026, 08:42 PM UTC

   The status updates have been completed. Developers are currently running a sync at this point to complete the fix. The ETA for this sync is around 1 hour.

7. resolved Sep 03, 2026, 09:41 PM UTC

   The Monthly Sync has been completed and the issue is currently resolved.

Read the full incident report →

Started Aug 17, 2026, 01:18 PM UTC· resolved Aug 17, 2026, 06:30 PM UTC

1. investigating Aug 17, 2026, 01:18 PM UTC

   You may be experiencing an unexpected loss of access or issues with your insights profile. This is actively being looked into and resolved by our team. We will provide regular progress updates as we look to resolve this issue. We apologize for any inconvenience this may have caused, and appreciate your patience.

2. investigating Aug 17, 2026, 04:32 PM UTC

   Our Technical team has identified the cause and is working to resolve the access issues through a data update. The ETA to complete the data upload and resolve the issue is within the next two hours. Thank you for your patience.

3. identified Aug 17, 2026, 05:51 PM UTC

   Our Technical team has restored access for 75% of the users for ClaimSearch Insights and is actively working to restore access for the remaining users. We expect access to be fully restored within the next hour.

4. resolved Aug 17, 2026, 06:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 04:47 PM UTC· resolved Jul 24, 2026, 06:00 PM UTC

1. investigating Jul 24, 2026, 04:47 PM UTC

   Our technical teams, along with the AWS vendor, are actively troubleshooting the issue to identify the root cause. We appreciate your patience and understanding while we work to resolve it as quickly as possible.

2. monitoring Jul 24, 2026, 05:46 PM UTC

   Our technical teams have identified the cause of the high system load and have deployed a fix. ClaimSearch website logins are now functioning normally. We will continue to monitor the application's stability to ensure the issue has been fully resolved.

3. resolved Jul 24, 2026, 06:00 PM UTC

   The incident has been resolved, and the affected services are operating normally. Thank you for your patience and understanding throughout this incident.

Read the full incident report →

Started Jul 23, 2026, 06:47 PM UTC· resolved Jul 23, 2026, 09:03 PM UTC

1. investigating Jul 23, 2026, 06:47 PM UTC

   We're actively investigating the disruption with ClaimSearch webiste and appreciate your patience as we work to identify the root cause.

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

   Our technical teams are actively working to increase the capacity of the application servers to improve system performance. Thank you for your patience and understanding.

3. monitoring Jul 23, 2026, 08:35 PM UTC

   Application response times have returned to normal. Our technical teams are actively monitoring the application to ensure services remain stable. Thank you for your patience.

4. monitoring Jul 23, 2026, 08:36 PM UTC

   We've identified the cause for the ClaimSearch website disruption and are actively working on implementing a solution.

5. resolved Jul 23, 2026, 09:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2026, 06:29 PM UTC· resolved Jul 16, 2026, 06:45 PM UTC

1. monitoring Jul 16, 2026, 06:29 PM UTC

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

2. resolved Jul 16, 2026, 06:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 04:50 PM UTC· resolved Jun 12, 2026, 09:05 PM UTC

1. investigating Jun 12, 2026, 04:50 PM UTC

   We are currently investigating this issue: we apologize for any inconvenience

2. monitoring Jun 12, 2026, 05:40 PM UTC

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

3. monitoring Jun 12, 2026, 05:41 PM UTC

   We are continuing to monitor for any further issues.

4. monitoring Jun 12, 2026, 06:03 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Jun 12, 2026, 09:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 03, 2026, 08:39 PM UTC· resolved Jun 04, 2026, 01:17 AM UTC

1. investigating Jun 03, 2026, 08:39 PM UTC

   Investigating: ClaimSearch Web match reports may be experience delays in posting to the website. We are currently investigating the issue. We apologize for any inconvenience and delays this may cause your processing.

2. resolved Jun 04, 2026, 01:17 AM UTC

   The potential delays with ClaimSearch Web match reports issue has been resolved. We apologize for any inconvenience

Read the full incident report →

Started May 22, 2026, 03:13 PM UTC· resolved May 26, 2026, 07:46 PM UTC

1. identified May 22, 2026, 03:13 PM UTC

   Claims Page may be experiencing some delays. If you run into an error, please clear your cache and refresh the page. We appreciate your patience as we work through resolution.

2. identified May 22, 2026, 03:14 PM UTC

   We are continuing to work on a fix for this issue.

3. identified May 22, 2026, 03:20 PM UTC

   We are continuing to work on a fix for this issue.

4. identified May 22, 2026, 03:28 PM UTC

   We are continuing to work on a fix for this issue.

5. resolved May 26, 2026, 07:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2026, 01:52 PM UTC· resolved Apr 16, 2026, 01:52 PM UTC

1. resolved Apr 16, 2026, 01:52 PM UTC

   This issue has been resolved. The Providers Page and Scorecard experienced a data load issue yesterday. We resolved the issue however data has not completed loading into the Providers Page and Scorecard, and will finish within the next few hours. Due to this, users may experience temporary incompleteness in their data within the two pages. Provider Scoring Insights is fully functional, and can leveraged as a workaround. We apologize for any inconvenience

Read the full incident report →

Started Mar 16, 2026, 01:25 PM UTC· resolved Mar 18, 2026, 02:01 PM UTC

1. identified Mar 16, 2026, 01:25 PM UTC

   The Provider Scoring Service is operational but displayed data may not be up to date. We are currently working to resolve this issue. We apologize for any inconvenience.

2. resolved Mar 18, 2026, 02:01 PM UTC

   This incident has been resolved. All data in Provider Scoring Insights is up to date. We apologize for any inconvenience.

Read the full incident report →

Started Jan 20, 2026, 05:42 PM UTC· resolved Jan 20, 2026, 09:47 PM UTC

1. investigating Jan 20, 2026, 05:42 PM UTC

   We are investigating an issue with ClaimSearch Login. Some users may be unable to login. We thank you for your patience while we investigate this issue.

2. monitoring Jan 20, 2026, 07:06 PM UTC

   Monitoring: A fix has been implemented and we are monitoring the ClaimSearch Services. We apologize for any inconvenience

3. resolved Jan 20, 2026, 09:47 PM UTC

   The incident with ClaimSearch Web Login has been resolved. We apologize for any inconvenience.

Read the full incident report →

Started Jan 14, 2026, 03:03 PM UTC· resolved Jan 15, 2026, 08:56 PM UTC

1. monitoring Jan 14, 2026, 03:03 PM UTC

   We are monitoring a delay in processing messages received from the NCIC. This may cause delays for ClaimSearch records getting updated with the accurate NCIC status.

2. resolved Jan 15, 2026, 08:56 PM UTC

   Resolved: All ClaimSearch records will now reflect an accurate NCIC Status. We apologize for any inconvenience

Read the full incident report →

Started Nov 19, 2025, 03:12 PM UTC· resolved Nov 19, 2025, 03:31 PM UTC

1. investigating Nov 19, 2025, 03:12 PM UTC

   We are currently investigating an issue with ClaimSearch Login. We apologize for any inconvenience

2. resolved Nov 19, 2025, 03:31 PM UTC

   This incident has been resolved. Thank you for your patience during this outage. We apologize for any inconvenience.

Read the full incident report →

Started Nov 18, 2025, 02:47 PM UTC· resolved Nov 18, 2025, 03:21 PM UTC

1. investigating Nov 18, 2025, 02:47 PM UTC

   We are currently investigating the unavailability of some searches within Research Hub. We apologize for any inconvenience

2. resolved Nov 18, 2025, 03:21 PM UTC

   This incident has been resolved. We apologize for any inconvenience

Read the full incident report →

Started Nov 07, 2025, 04:13 PM UTC· resolved Nov 07, 2025, 05:59 PM UTC

1. investigating Nov 07, 2025, 04:13 PM UTC

   We apologize for the inconvenience. We are working to identify and resolve this issue.

2. investigating Nov 07, 2025, 04:58 PM UTC

   We have implemented a fix for the Degraded Performance with ClaimSearch Login and the other services impacted. We apologize for any inconvenience. We are actively monitoring to insure service stability.

3. resolved Nov 07, 2025, 05:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 03:59 PM UTC· resolved Oct 21, 2025, 01:32 PM UTC

1. investigating Oct 20, 2025, 09:28 AM UTC

   Our applications are hosted in the AWS environment. AWS is currently experiencing an outage, and the AWS vendor is working to resolve the issue. Meanwhile, we are working on identifying and implementing an alternative solution.

2. investigating Oct 20, 2025, 09:49 AM UTC

   AWS vendor has recovered most of the impacted services. We have validated that significant functionalities are operational, and we are continuing to validate the application to ensure all apps are stable.

3. investigating Oct 20, 2025, 10:55 AM UTC

   We are still experiencing issues with some of the functionalities in the Anti Fraud Analytics and Casualty Solutions application, and our technical teams are actively working to resolve them. Thank you for your patience.

4. investigating Oct 20, 2025, 11:49 AM UTC

   Currently, the AWS vendor is actively working to resolve the issues with starting the affected application servers. Meanwhile, our technical teams are also working on an alternative solution to restore the impacted applications. We will continue our efforts to bring the applications back online.

5. investigating Oct 20, 2025, 12:53 PM UTC

   AWS vendor has fixed some of the application servers and they are still working on fixing the remaining servers. The issue is expected to be resolved within an hour. Thank you for your patience.

6. identified Oct 20, 2025, 01:11 PM UTC

   Our technical teams have implemented the workaround solution recommended by the AWS vendor. As a result, we have successfully restarted a portion of the affected application servers. The teams are continuing to work on bringing up the remaining impacted servers, and full recovery is expected soon.

7. identified Oct 20, 2025, 02:06 PM UTC

   Our technical teams are actively collaborating with the AWS vendor, applying vendor-recommended fixes, and taking the necessary steps to restore full functionality as quickly as possible. We appreciate your understanding.

8. identified Oct 20, 2025, 02:39 PM UTC

   Investigating : Claim Search website is currently unavailable to a major outage. We appreciate your patience as we work to identify the root cause.

9. identified Oct 20, 2025, 03:30 PM UTC

   The AWS vendor is continuing to investigate the underlying cause of the networking issues and issues with starting up application servers. In parallel, Verisk technical teams are working on failover efforts to an alternate stable AWS environment to restore services as quickly as possible. We will provide further updates as progress is made. We appreciate your understanding while we work to fully resolve this issue.

10. identified Oct 20, 2025, 03:59 PM UTC

    We are continuing to work on a fix for this issue in close collaboration with the AWS vendor. Our teams are actively implementing vendor-recommended actions.

11. identified Oct 20, 2025, 04:35 PM UTC

    The AWS vendor is taking additional steps to fully resolve the ongoing networking connectivity issues. In parallel, they are actively working to address challenges impacting the launch of new application servers, which is required to restore normal capacity. We are closely monitoring progress and will continue to provide updates until services are fully stabilized.

12. identified Oct 20, 2025, 05:32 PM UTC

    The AWS vendor continues to implement mitigation steps to resolve issues with launching application servers and networking. In parallel, Verisk technical teams are working on failover to the standby environment for the affected services to restore functionality.

13. identified Oct 20, 2025, 07:41 PM UTC

    The AWS vendor has deployed a fix to address issues with application server launches and is continuing to work on resolving the networking issue. We are still observing intermittent performance issues with the AntiFraud applications. We appreciate your patience.

14. monitoring Oct 20, 2025, 08:08 PM UTC

    The AWS vendor has implemented a fix for the networking issue, and systems are recovering. The ClaimSearch website and Claims Inquiry are operational. Claims Submission and Match Reports are processing, but it will take some time for the queues to fully catch up.

15. monitoring Oct 20, 2025, 09:51 PM UTC

    The AWS vendor is continuing to work on resolving issues with starting up additional serverless application servers. We are actively monitoring the queues to ensure claims are being processed in the AntiFraud Analytics applications. Thank you for your patience.

16. monitoring Oct 20, 2025, 11:24 PM UTC

    We are continuing to monitor for any further issues. We have scaled up our resources as we process through the backlog. Thank you for your patience as we work through this issue.

17. resolved Oct 21, 2025, 01:32 PM UTC

    This incident is resolved and all services are operational. We apologize for any inconvenience.

Read the full incident report →

Started Aug 19, 2025, 05:25 PM UTC· resolved Aug 20, 2025, 06:53 PM UTC

1. investigating Aug 19, 2025, 05:25 PM UTC

   We are currently investigating this issue. We apologize for any inconvenience

2. monitoring Aug 19, 2025, 11:26 PM UTC

   We have identified the issue and are working through any backlog. We are monitoring all transmissions for validity. Thank you for your patience and we apologize for any inconvenience.

3. resolved Aug 20, 2025, 06:53 PM UTC

   RESOLVED: If your company did not receive an FTP Match Response File (CSUSUFOT) yesterday, the file was posted at this morning with an 8/19 date stamp. Today's files were also posted as expected. You may need to run an extra pick-up job to pick up both files. We apologize for any inconvenience

Read the full incident report →

Started Aug 05, 2025, 02:40 PM UTC· resolved Aug 05, 2025, 10:23 PM UTC

1. investigating Aug 05, 2025, 02:40 PM UTC

   This issue is actively being investigated. Thank you for your patience.

2. identified Aug 05, 2025, 03:56 PM UTC

   The issue has been identified and a fix is being implemented. Thank you for your patience and we apologize for any inconvenience.

3. resolved Aug 05, 2025, 10:23 PM UTC

   This incident is resolved - thank you for your patience and we apologize for any inconvenience

Read the full incident report →