Identifi had 20 outages in the last 2 years totaling 3255h 47m of downtime — averaging 0.8 incidents per month.
There were 20 Identifi outages since August 16, 2024 totaling 3255h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Identifi is aware that some automated jobs are not completing as expected. We are investigating.
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.
This incident has been resolved.
We are aware that customers may be unable to connect. We are investigating.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
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.
All services remain operational. Root Cause Analysis will be published when available.
Identifi is aware of issues with Workflow and Add Documents. As we continue to investigate, end users can try resetting their browser cache.
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.
Identifi is aware that all of our Canadian customers cannot access the system. We are actively investigating.
The Identifi team is continuing to investigate the issue.
Identifi believes that we have found the issue. Access should be restored. Please contact Support if you encounter any problems.
This incident has been resolved.
**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.
We are investigating an issue where customers are unable to view batches in version 25.3.
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.
This incident has been resolved. All settings have been updated to allow batches to be viewed with no error messages.
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.
We are continuing to investigate this issue.
The majority of customers are now able to access their Identifi system. Estimated time for complete access is 7 PM EDT.
All customers are now able to access their Identifi system.
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.
Identifi has observed an issue accessing most customer installations. Also, some reports and BLIs may be delayed. We are investigating.
This incident has been resolved. Any delayed jobs will re-run. Identifi will investigate the root cause.
We are observing intermittent backend connectivity issues. Job processing is also impacted. Identifi is investigating.
This issue has been resolved. Any delayed reports will start showing up over time this morning.
We are aware of indexing delays for some customers. Identifi staff is working to resolve these delays.
This incident has been resolved.
We are getting reports various issues with logging in and creating/indexing batches. We are investigating.
We are continuing to investigate this issue.
We have identified the issue and have implemented a fix. All services have been restored.
This incident has been resolved and an RCA will available shortly.
We are investigating multiple customers unable to connect to their Identifi installation. We are investigating.
The issue has been identified and connectivity has been restored. An RCA will be posted as soon as we have more details,
This incident has been resolved.
SQL server was unexpectedly rebooted.
Hurricane Helena is expected to impact the Florida panhandle some time on Thursday (9/26) or early Friday. Impacts are likely to be felt in the Tampa Bay area (where Identifi is headquartered) starting on Thursday. We do not expect any service interruptions. Our datacenter facility is hardened against the type of weather we expect to encounter. However, we may face staffing issues as employees deal with any local effects.
We are continuing to monitor the storm. The latest forecast indicates that the greatest impacts to the Tampa Bay area are expected on Thursday starting late morning and continuing into the evening.
We are continuing to monitor for any further issues.
The storm passed by the Tampa Bay area on Thursday and Friday. There were no impacts to Identifi operations.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The event was caused because a set of security certificates within our orchestration system expired at the same time. This caused the web servers to stop. We regenerated those certificates and brought the orchestration system back to working order. To prevent this from happening again, we have setup reminders to regenerate those certificates before they expire.
We are currently investigating.
We have identified the issue and have implemented a fix.
We are continuing to monitor for any further issues.
This also impacted importing of reports. We are working to reprocess as soon as possible.
We are continuing to monitor for any further issues.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to investigate a fix for this issue.
A fix has been implemented and we will continue to monitor.
This incident has been resolved.
At approximately 11:20 AM US ET \(15:20 UTC\) on August 16, 2024, Identifi observed that a sub-set of customers hosted in our Azure infrastructure were not available. Identifi staff began troubleshooting the issue. By approximately 12:45 PM US ET Identifi staff found and resolved the problem. All impacted customers were brought back online within 10 minutes. Root Cause An internal Encryption Key expired resulting in a failure of the Identifi Product to connect to databases and process cookies. Lessons Learned and Process Improvements Identifi has found the cloud resource that caused key ring failures during key rotation. We have added proper permissions and resolved the issue. Additional monitoring has been put in place to warn of any future issues of this type.