Identifi Outage History

Started Apr 14, 2026, 02:44 PM UTC· resolved Aug 04, 2026, 01:50 PM UTC

1. identified Apr 14, 2026, 02:44 PM UTC

   We are currently aware of an issue affecting some customers where BLI data is not synchronizing as expected. Our team is actively working to resolve this matter. We will continue to provide updates on this status page as more information becomes available.

2. identified Apr 14, 2026, 02:44 PM UTC

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

3. resolved Aug 04, 2026, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 24, 2026, 02:42 PM UTC· resolved Mar 30, 2026, 01:43 PM UTC

1. investigating Mar 24, 2026, 02:42 PM UTC

   Identifi is aware of intermittent slow performance. We are actively investigating.

2. investigating Mar 24, 2026, 06:35 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 24, 2026, 08:56 PM UTC

   We have been actively monitoring the situation and working with customers throughout the day; however, a root cause has not yet been identified. If you are experiencing this issue and have not already contacted Support, please email [email protected] so we can further investigate. At this time, the issue appears to be intermittent and does not impact all users or environments. We will continue to monitor the situation and provide updates as more information becomes available.

4. investigating Mar 25, 2026, 01:57 PM UTC

   Identifi continues to monitor and investigate this issue. It remains an intermittent condition. Some end users report that closing and restarting the browser can help. If you are experiencing this issue and have not already contacted Support, please email [email protected] so we can further investigate. When you contact Support, please provide detailed information about which function you are using and where you are experiencing an issue. Unless there is new information sooner, we will post another update at 12:00 PM US ET (16:00 UTC).

5. investigating Mar 25, 2026, 04:15 PM UTC

   Our team is actively monitoring and investigating this intermittent issue. If you haven't already reached out, please email [email protected] and include details about the specific function and location where you're experiencing the issue — this will help us investigate more effectively. Barring any new developments, our next update will be posted at 4:00 PM US ET (20:00 UTC).

6. investigating Mar 25, 2026, 08:54 PM UTC

   Our team continues to monitor and investigate the intermittent issue. As part of our ongoing efforts, we will be performing a reboot of a core VPN device after 11:00 PM ET tonight. This device supports all VPN connections, and we are taking this step to rule out the VPN connection as the root cause. We will provide further updates as more information becomes available.

7. investigating Mar 26, 2026, 02:39 PM UTC

   The VPN device restart completed last night does not appear to have resolved the intermittent issue. Our next step is to implement a configuration change to the VPN device, which will be service-impacting. We currently plan to perform this change after hours, beginning at 11:00 PM ET (03:00 UTC). In the meantime, please share the following guidance with any users experiencing intermittent issues: ** If an error occurs while loading an image, please refresh or restart your browser. ** If you are indexing a batch and experiencing latency on a file, please allow additional time for the image to load. ** If attributes are not displaying while indexing a batch, please click back and then forward to reload the screen. If you are experiencing this issue and have not yet notified our Support team, please email [email protected] so we can log your organization as impacted. This information helps us better understand the scope of the issue and identify patterns as we continue troubleshooting. We will provide further updates as more information becomes available.

8. monitoring Mar 27, 2026, 01:21 PM UTC

   The configuration change applied overnight appears to have improved performance. Identifi will continue to monitor as traffic increases throughout the day.

9. resolved Mar 30, 2026, 01:43 PM UTC

   This incident has been resolved. A root cause analysis will follow.

10. postmortem Mar 30, 2026, 02:20 PM UTC

    **Root Cause** Our investigation determined that the virtual machine \(VM\) powering the network appliance responsible for terminating customer VPN connections experienced CPU resource throttling on the underlying Azure infrastructure. This throttling degraded the appliance's ability to process network traffic, resulting in connection drops and packet loss for affected customers. To resolve the issue, Identifi migrated the appliance to an Azure VM type that is not subject to resource throttling. **What We're Doing to Prevent Recurrence** Identifi has implemented dedicated resource monitoring and alerting for this VM, enabling our team to detect and respond to similar infrastructure conditions before they impact customers.

Read the full incident report →

Started Mar 18, 2026, 02:25 PM UTC· resolved Mar 19, 2026, 02:50 AM UTC

1. investigating Mar 18, 2026, 02:25 PM UTC

   Identifi is aware that some automated jobs are not completing as expected. We are investigating.

2. monitoring Mar 18, 2026, 02:50 PM UTC

   The system is operating as expected at this time. The issue appeared to be related to an issue accessing temporary files from an internal location. Identifi has implemented a fix and we will continue to monitor.

3. resolved Mar 19, 2026, 02:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2026, 03:04 PM UTC· resolved Feb 24, 2026, 06:29 PM UTC

1. investigating Feb 24, 2026, 03:04 PM UTC

   We are aware that customers may be unable to connect. We are investigating.

2. investigating Feb 24, 2026, 03:05 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 24, 2026, 03:07 PM UTC

   We are continuing to investigate this issue.

4. investigating Feb 24, 2026, 04:00 PM UTC

   Update: Access to instances should be available at this time. We think that we have identified the issue and have paused the jobs that import data into the system. We continue to troubleshoot, and access may be impacted as we work on the issue.

5. resolved Feb 24, 2026, 06:29 PM UTC

   All services remain operational. Root Cause Analysis will be published when available.

Read the full incident report →

Started Oct 16, 2025, 04:52 PM UTC· resolved Oct 16, 2025, 05:11 PM UTC

1. investigating Oct 16, 2025, 04:52 PM UTC

   Identifi is aware of issues with Workflow and Add Documents. As we continue to investigate, end users can try resetting their browser cache.

2. resolved Oct 16, 2025, 05:11 PM UTC

   After investigation it has been determined that customers that were recently upgraded will need to clear the browser cache on each end user work station.

Read the full incident report →

Started Sep 05, 2025, 11:13 AM UTC· resolved Sep 05, 2025, 01:16 PM UTC

1. investigating Sep 05, 2025, 11:13 AM UTC

   Identifi is aware that all of our Canadian customers cannot access the system. We are actively investigating.

2. investigating Sep 05, 2025, 12:11 PM UTC

   The Identifi team is continuing to investigate the issue.

3. investigating Sep 05, 2025, 01:13 PM UTC

   Identifi believes that we have found the issue. Access should be restored. Please contact Support if you encounter any problems.

4. resolved Sep 05, 2025, 01:16 PM UTC

   This incident has been resolved.

5. postmortem Sep 05, 2025, 06:23 PM UTC

   **Incident Summary** On September 5, 2025, at approximately 6:00 AM US ET \(11:00 UTC\), Identifi became aware of an issue affecting access to tenants within our Canadian Microsoft Azure infrastructure. The incident investigation began at 7:00 AM US ET, and normal operations were fully restored by 9:15 AM US ET. **Root Cause** Azure applied updates to the Identifi hosting infrastructure, which inadvertently exposed a networking configuration issue that disrupted connectivity to a back-end resource. **Resolution and Next Steps** * Identifi has implemented a networking change to address and mitigate the identified issue. * A scheduled process will be established to better manage and control the timing of Azure updates to reduce the risk of recurrence. * Lessons learned from this incident will be incorporated into Identifi’s ongoing infrastructure monitoring and update management practices.

Read the full incident report →

Started Aug 07, 2025, 04:06 PM UTC· resolved Aug 07, 2025, 09:45 PM UTC

1. investigating Aug 07, 2025, 04:06 PM UTC

   We are investigating an issue where customers are unable to view batches in version 25.3.

2. identified Aug 07, 2025, 04:39 PM UTC

   We have identified the issue and are working on a backed fix. In the meantime, you can resolve the issue by setting your "COLD Viewer Zoom Default", "Document Viewer Zoom Default" to your preferred setting in the Preferences Page of the User Profile (click the person icon in the top right corner > Select Settings > Select Preferences). If the Preferences Page is not visible, you may need to clear your browser Cache and Cookies. We will post an update once the backed fix has been applied and follow up with an RCA once everything has been finalized.

3. resolved Aug 07, 2025, 09:45 PM UTC

   This incident has been resolved. All settings have been updated to allow batches to be viewed with no error messages.

Read the full incident report →

Started Jul 18, 2025, 09:30 PM UTC· resolved Jul 18, 2025, 10:10 PM UTC

1. investigating Jul 18, 2025, 09:30 PM UTC

   We're currently experiencing a partial outage affecting some of our customers. Our team is actively investigating and working to resolve the issue as quickly as possible. We’ll provide updates as more information becomes available. Thank you for your patience.

2. investigating Jul 18, 2025, 09:41 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 18, 2025, 10:06 PM UTC

   The majority of customers are now able to access their Identifi system. Estimated time for complete access is 7 PM EDT.

4. resolved Jul 18, 2025, 10:10 PM UTC

   All customers are now able to access their Identifi system.

5. postmortem Jul 22, 2025, 08:26 PM UTC

   On Friday, July 18th, at approximately 2:15 PM EST, Identifi began receiving reports of intermittent timeouts impacting user access. Our investigation determined that a key backend resource had become unresponsive. The affected resource was restored by 5:30 PM EST, and full access to all installations was confirmed by 6:15 PM EST. To prevent future issues, we have implemented enhanced monitoring to detect early signs of similar timeout conditions. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to resolve the issue.

Read the full incident report →

Started Jun 20, 2025, 12:52 PM UTC· resolved Jun 22, 2025, 12:40 PM UTC

1. investigating Jun 20, 2025, 12:52 PM UTC

   Identifi is aware of an intermittent issue with login and application navigation.

2. investigating Jun 20, 2025, 12:52 PM UTC

   We are continuing to investigate this issue.

3. investigating Jun 20, 2025, 02:40 PM UTC

   We are continuing to investigate the issue and are closing in on a possible cause.

4. investigating Jun 20, 2025, 03:30 PM UTC

   We are still investigating. A workaround would be to refresh or retry any operation until it completes.

5. investigating Jun 20, 2025, 03:58 PM UTC

   Investigation continues. We are going to restart the web services. This may cause a short disruption for all users.

6. investigating Jun 20, 2025, 04:29 PM UTC

   Investigation continues. The restart was completed, however the issue continues.

7. investigating Jun 20, 2025, 05:57 PM UTC

   We are still investigating. A workaround would be to refresh or retry any operation until it completes.

8. investigating Jun 20, 2025, 06:48 PM UTC

   We are still investigating. A workaround would be to refresh or retry any operation until it completes.

9. monitoring Jun 20, 2025, 07:52 PM UTC

   We believe that we've isolated the problem and have restored normal operations. We will continue to monitor.

10. resolved Jun 22, 2025, 12:40 PM UTC

    This incident has been resolved.

11. postmortem Jun 23, 2025, 04:45 PM UTC

    At approximately 8:15 AM US ET \(12:15 PM UTC\) on June 20, 2025, a service disruption occurred due to unexpected errors that triggered degraded performance within the shared environment. The intermittent outage was resolved at approximately 3:52 PM US ET. Root Cause Missing configuration files in a new customer environment caused unexpected errors that impacted the performance and availability of other users. Resolution, Lessons Learned, and Process Improvements The missing configuration files were restored and the issue resolved. We’ve updated our onboarding process to ensure all required configurations are complete before a customer goes live. We’ve also implemented safeguards to prevent similar issues from impacting other users in the future. – Identifi Cloud Team

Read the full incident report →

Started Apr 20, 2025, 04:12 PM UTC· resolved Apr 20, 2025, 05:32 PM UTC

1. investigating Apr 20, 2025, 04:12 PM UTC

   Identifi has observed an issue accessing most customer installations. Also, some reports and BLIs may be delayed. We are investigating.

2. resolved Apr 20, 2025, 05:32 PM UTC

   This incident has been resolved. Any delayed jobs will re-run. Identifi will investigate the root cause.

Read the full incident report →

Started Apr 16, 2025, 12:11 PM UTC· resolved Apr 16, 2025, 12:48 PM UTC

1. investigating Apr 16, 2025, 12:11 PM UTC

   We are observing intermittent backend connectivity issues. Job processing is also impacted. Identifi is investigating.

2. resolved Apr 16, 2025, 12:48 PM UTC

   This issue has been resolved. Any delayed reports will start showing up over time this morning.

Read the full incident report →

Started Mar 10, 2025, 02:11 PM UTC· resolved Mar 11, 2025, 01:19 PM UTC

1. identified Mar 10, 2025, 02:11 PM UTC

   We are aware of indexing delays for some customers. Identifi staff is working to resolve these delays.

2. resolved Mar 11, 2025, 01:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2025, 05:03 PM UTC· resolved Mar 05, 2025, 08:35 PM UTC

1. investigating Mar 05, 2025, 05:03 PM UTC

   We are getting reports various issues with logging in and creating/indexing batches. We are investigating.

2. investigating Mar 05, 2025, 05:16 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 05, 2025, 05:19 PM UTC

   We have identified the issue and have implemented a fix. All services have been restored.

4. resolved Mar 05, 2025, 08:35 PM UTC

   This incident has been resolved and an RCA will available shortly.

Read the full incident report →

Started Jan 08, 2025, 02:58 PM UTC· resolved Jan 08, 2025, 04:21 PM UTC

1. investigating Jan 08, 2025, 02:58 PM UTC

   We are investigating multiple customers unable to connect to their Identifi installation. We are investigating.

2. monitoring Jan 08, 2025, 03:05 PM UTC

   The issue has been identified and connectivity has been restored. An RCA will be posted as soon as we have more details,

3. resolved Jan 08, 2025, 04:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 30, 2024, 11:30 AM UTC· resolved Oct 30, 2024, 11:30 AM UTC

1. resolved Oct 31, 2024, 04:46 PM UTC

   SQL server was unexpectedly rebooted.

Read the full incident report →