Unit21 AI had 13 outages in the last 2 years totaling 28h 42m of downtime — averaging 0.5 incidents per month.
There were 13 Unit21 AI outages since July 7, 2025 totaling 28h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
The partial outage with Auth0 has been resolved, and all login services are operating normally. During the incident, some users may have experienced errors when attempting to log in to Unit21. Please note that access via Magic Link was unaffected throughout this time. Thank you for your patience. Auth0 Incident page: https://status.auth0.com/incidents/z8sc9m1gzqb7
Webhooks service is currently experiencing a service disruption. The issue has been identified and a fix is being identified
Webhooks service is currently experiencing a service disruption. The issue has been identified and a fix is being identified
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Fix has been identified and deployed
This incident has been resolved.
Databricks Compute and Lakeflow is down. This impacts the following features: - file exports - watchlist We are monitoring updates from Databricks.
Databricks have restored their services. Incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We have identified an issue with Transaction Sanction Monitoring related to our 3rd party provider. A fix is currently underway.
This incident has been resolved.
Rule scheduling and processing are temporarily delayed. We are actively working to resolve this.
Rules are experiencing delays due to a recent system update. We will be rolling out a fix shortly.
The fix has been deployed, and we’re monitoring to ensure everything is working as expected.
This incident has been resolved.
We are investigating reports that 314(a) scans cannot be created for the 314(a) person and business files released on Nov. 11, 2025, due to an unannounced change in file format.
We are continuing to investigate reports that 314(a) scans cannot be created for the 314(a) person and business files released on Nov. 11, 2025, due to an unannounced change in file format.
The issue has been identified and we are working on a fix.
This incident has been resolved.
An internal routing update briefly caused errors for a subset of features for about 1 minute. The issue was quickly resolved; no data was lost and any affected jobs were automatically retried to completion. No customer action is required.
We are experiencing issues ingesting data due to database constraints. Rest assured we have a backup logging system to insure all data will be ingested eventually when the issue is resolved. Thank you for patience.
We are continuing to investigate this issue.
Rules and data ingestion services are back to operational.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.