- Detected by Pingoru
- Jul 24, 2026, 04:47 PM UTC
- Resolved
- Jul 24, 2026, 06:00 PM UTC
- Duration
- 1h 13m
Affected: ClaimSearch Website
Timeline · 3 updates
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Jul 23, 2026, 06:47 PM UTC
- Resolved
- Jul 23, 2026, 09:03 PM UTC
- Duration
- 2h 16m
Affected: ClaimSearch Website
Timeline · 5 updates
-
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.
-
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.
-
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.
-
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.
-
resolved Jul 23, 2026, 09:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 06:29 PM UTC
- Resolved
- Jul 16, 2026, 06:45 PM UTC
- Duration
- 16m
Affected: ClaimSearch Website
Timeline · 2 updates
-
monitoring Jul 16, 2026, 06:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 16, 2026, 06:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 04:50 PM UTC
- Resolved
- Jun 12, 2026, 09:05 PM UTC
- Duration
- 4h 15m
Affected: Claims Reporting - Web SubmissionClaims Reporting - Integrated Submission - XML
Timeline · 5 updates
-
investigating Jun 12, 2026, 04:50 PM UTC
We are currently investigating this issue: we apologize for any inconvenience
-
monitoring Jun 12, 2026, 05:40 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 12, 2026, 05:41 PM UTC
We are continuing to monitor for any further issues.
-
monitoring Jun 12, 2026, 06:03 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 12, 2026, 09:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:39 PM UTC
- Resolved
- Jun 04, 2026, 01:17 AM UTC
- Duration
- 4h 38m
Affected: ClaimSearch WebsiteClaimSearch Match Report
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- May 22, 2026, 03:13 PM UTC
- Resolved
- May 26, 2026, 07:46 PM UTC
- Duration
- 4d 4h
Affected: Claim ScoringProvider Scoring
Timeline · 5 updates
-
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.
-
identified May 22, 2026, 03:14 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 22, 2026, 03:20 PM UTC
We are continuing to work on a fix for this issue.
-
identified May 22, 2026, 03:28 PM UTC
We are continuing to work on a fix for this issue.
-
resolved May 26, 2026, 07:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 01:52 PM UTC
- Resolved
- Apr 16, 2026, 01:52 PM UTC
- Duration
- —
Affected: Provider Scoring
Timeline · 1 update
-
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 →
- Detected by Pingoru
- Mar 16, 2026, 01:25 PM UTC
- Resolved
- Mar 18, 2026, 02:01 PM UTC
- Duration
- 2d
Affected: Provider Scoring
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Jan 20, 2026, 05:42 PM UTC
- Resolved
- Jan 20, 2026, 09:47 PM UTC
- Duration
- 4h 4m
Affected: ClaimSearch Website
Timeline · 3 updates
-
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.
-
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
-
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 →
- Detected by Pingoru
- Jan 14, 2026, 03:03 PM UTC
- Resolved
- Jan 15, 2026, 08:56 PM UTC
- Duration
- 1d 5h
Affected: NICB
Timeline · 2 updates
-
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.
-
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 →
- Detected by Pingoru
- Nov 19, 2025, 03:12 PM UTC
- Resolved
- Nov 19, 2025, 03:31 PM UTC
- Duration
- 18m
Affected: ClaimSearch Website
Timeline · 2 updates
-
investigating Nov 19, 2025, 03:12 PM UTC
We are currently investigating an issue with ClaimSearch Login. We apologize for any inconvenience
-
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 →
- Detected by Pingoru
- Nov 18, 2025, 02:47 PM UTC
- Resolved
- Nov 18, 2025, 03:21 PM UTC
- Duration
- 33m
Affected: Research Hub
Timeline · 2 updates
-
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
-
resolved Nov 18, 2025, 03:21 PM UTC
This incident has been resolved. We apologize for any inconvenience
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2025, 04:13 PM UTC
- Resolved
- Nov 07, 2025, 05:59 PM UTC
- Duration
- 1h 45m
Affected: ClaimSearch WebsiteClaims Reporting - Web SubmissionResearch Hub
Timeline · 3 updates
-
investigating Nov 07, 2025, 04:13 PM UTC
We apologize for the inconvenience. We are working to identify and resolve this issue.
-
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.
-
resolved Nov 07, 2025, 05:59 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 03:59 PM UTC
- Resolved
- Oct 21, 2025, 01:32 PM UTC
- Duration
- 21h 32m
Affected: ClaimSearch WebsiteDiscovery NavigatorClaimSearch Match ReportClaims InquiryClaims Reporting - Web SubmissionClaims Reporting - Integrated Submission - XMLNICBwcPrism
Timeline · 17 updates
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 05:25 PM UTC
- Resolved
- Aug 20, 2025, 06:53 PM UTC
- Duration
- 1d 1h
Affected: Claims Reporting - Integrated Submission - FTP
Timeline · 3 updates
-
investigating Aug 19, 2025, 05:25 PM UTC
We are currently investigating this issue. We apologize for any inconvenience
-
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.
-
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 →
- Detected by Pingoru
- Aug 05, 2025, 02:40 PM UTC
- Resolved
- Aug 05, 2025, 10:23 PM UTC
- Duration
- 7h 42m
Affected: ClaimSearch Insights (Dashboards)
Timeline · 3 updates
-
investigating Aug 05, 2025, 02:40 PM UTC
This issue is actively being investigated. Thank you for your patience.
-
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.
-
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 →
- Detected by Pingoru
- Jul 30, 2025, 03:23 PM UTC
- Resolved
- Jul 30, 2025, 10:22 PM UTC
- Duration
- 6h 59m
Affected: Claims Reporting - Web SubmissionClaims Reporting - Integrated Submission - XML
Timeline · 3 updates
-
investigating Jul 30, 2025, 03:23 PM UTC
We are currently investigating an issue delaying Claims Processing. These issues started last evening. We apologize for any inconvenience.
-
identified Jul 30, 2025, 05:49 PM UTC
We have identified the issue and are working on implementing a fix. Once the fix is implemented we need to process through the backlog. We do apologize for any inconvenience, and thank you for your continued patience.
-
resolved Jul 30, 2025, 10:22 PM UTC
This incident was resolved as of 4:30 PM ET. We apologize for any inconvenience
Read the full incident report →
- Detected by Pingoru
- Jul 28, 2025, 03:08 PM UTC
- Resolved
- Jul 28, 2025, 04:34 PM UTC
- Duration
- 1h 25m
Affected: Research Hub
Timeline · 3 updates
-
investigating Jul 28, 2025, 03:08 PM UTC
We are currently investigating this issue. We apologize for any inconvenience.
-
monitoring Jul 28, 2025, 03:41 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 28, 2025, 04:34 PM UTC
This incident has been resolved. We apologize for any inconvenience
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2025, 06:20 PM UTC
- Resolved
- Jul 16, 2025, 02:36 PM UTC
- Duration
- 20h 16m
Affected: Claims Reporting - Web SubmissionClaims Reporting - Integrated Submission - XML
Timeline · 4 updates
-
identified Jul 15, 2025, 06:20 PM UTC
XML Responses will be delayed up to 30 minutes. Our technical teams have identified the issue, and is implementing a solution to fully restore service - We apologize for any inconvenience.
-
monitoring Jul 15, 2025, 06:51 PM UTC
A fix has been implemented and queue depth is coming down. We will continue to monitor and send an update when all queues have been cleared. We apologize for any inconvenience
-
monitoring Jul 15, 2025, 08:34 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 16, 2025, 02:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 15, 2025, 05:15 PM UTC
- Resolved
- May 15, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 15, 2025, 05:15 PM UTC
Our Technical team has identified the issue and are currently backed out the update that caused the issue. The teams are actively monitoring system stability to ensure continued performance. Thank you for your understanding.
Read the full incident report →
- Detected by Pingoru
- May 13, 2025, 12:00 PM UTC
- Resolved
- May 13, 2025, 12:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 13, 2025, 01:47 PM UTC
Research Hub is currently experiencing an outage associated with the public records products within the People/Basic Search, Assets, Businesses, and Directly Assistance sections as well as the Vehicle Search in the Vehicle Data section. We are actively working to fix the issue.
Read the full incident report →
- Detected by Pingoru
- May 01, 2025, 03:36 PM UTC
- Resolved
- May 01, 2025, 06:58 PM UTC
- Duration
- 3h 21m
Affected: ClaimSearch Website
Timeline · 4 updates
-
investigating May 01, 2025, 03:36 PM UTC
We’re investigating a potential login issue with the ClaimSearch website, and XML Web Service processing. Our Technical team is working to resolve it as quickly as possible. Thank you for your patience.
-
investigating May 01, 2025, 05:02 PM UTC
Our Technical team has identified a capacity issue and increased the capacity of the impacted services. The teams are actively monitoring system stability to ensure continued performance. Thank you for your understanding.
-
monitoring May 01, 2025, 05:52 PM UTC
The fix has been implemented, and our technical teams are continuing to monitor the stability of the application.
-
resolved May 01, 2025, 06:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2025, 02:55 PM UTC
- Resolved
- Apr 11, 2025, 10:58 PM UTC
- Duration
- 8h 2m
Affected: Other ClaimSearch Services
Timeline · 2 updates
-
investigating Apr 11, 2025, 02:55 PM UTC
We apologize for any inconvenience this is causing. Rest assured, we are treating this with the highest priority and will update you once we've identified the root cause.
-
resolved Apr 11, 2025, 10:58 PM UTC
This incident is resolved. we apologize for any inconvenience
Read the full incident report →
- Detected by Pingoru
- Mar 21, 2025, 04:21 PM UTC
- Resolved
- Mar 24, 2025, 01:37 PM UTC
- Duration
- 2d 21h
Affected: Research Hub
Timeline · 2 updates
-
investigating Mar 21, 2025, 04:21 PM UTC
We apologize for any inconvenience this is causing. Rest assured, we're continue to treat this with the highest priority and will update you once we've identified the root cause.
-
resolved Mar 24, 2025, 01:37 PM UTC
This incident has been resolved. We apologize for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2025, 01:33 PM UTC
- Resolved
- Mar 11, 2025, 01:44 PM UTC
- Duration
- 11m
Affected: Claims Inquiry
Timeline · 2 updates
-
monitoring Mar 11, 2025, 01:33 PM UTC
Our Claims Inquiry serviced experienced a service disruption this morning due to a certificate update on our side.
-
resolved Mar 11, 2025, 01:44 PM UTC
This issue is resolved. We apologize for any inconvenience.
Read the full incident report →