Alloy Outage History

The issue is currently resolved. Socure DocV is available again. RCA is upcoming.

Between approximately 11:18 AM and 11:38 AM ET, some users experienced intermittent issues loading Workflows, Journeys, and Application Queues in the Alloy Dashboard. A fix has been rolled out and we have confirmed that the affected pages are loading normally.

We’ve identified the issue, deployed a fix, and confirmed export processing performance has returned to normal levels.

Between 12:45 PM and 1:20 PM ET on August 27, a third-party data provider Threatmetrix experienced a service disruption that caused intermittent connection errors on device intelligence checks. During this window, some evaluations that use impacted service completed as partial rather than returning a full provider response, and some requests saw elevated latency or connector timeouts. The provider has confirmed the underlying issue is resolved, and error rates returned to normal by 1:20 PM ET. Evaluations submitted outside this window were not affected.

Issue have been fully resolved. Elevated error rates were observed on August 25th between 14:18 and 14:22 PM ET and between 14:29 and 14:35 PM ET

This incident has been resolved.

The issue affecting the Journeys API has been fully resolved, and service has returned to normal. We have completed monitoring and confirmed that related dashboard functionality has also recovered as of July 21, 2026 at 5:11 PM ET. Thank you for your patience while we worked to restore service.

We have confirmed that login functionality and Application Queues have returned to normal operation, and no further impact is being observed. Thank you for your patience while we worked to resolve this issue.

We have seen recovery across the impacted LexisNexis services and error rates has returned to expected levels. This incident is now considered resolved. We will continue to work with the LexisNexis team to obtain a Root Cause Analysis (RCA). If you would like to receive a copy of the RCA when it becomes available, please contact [email protected].

After further montioring, we have not observed any new errors. All systems are operating normally.

Starting at 9:17 AM ET, the homepage analytics dashboards were not loading as expected. All other dashboard pages and services remained fully operational. As of 11:47 AM ET, the system has recovered and is fully operational.

We believe the cause of the latency is resolved.

The issue has been resolved.

We recently identified and resolved an issue affecting some plugins initialized through the Alloy SDK. For a subset of SDK Plugins, applications initializing the SDK may have experienced unexpected behavior, which could present as UI instability or premature close events. We mitigated the issue by rolling back a recent SDK change. Following the rollback, normal plugin behavior was restored. If you continue to experience any issues, please contact Alloy Support.

Between March 4 at 11:00 PM ET and March 5 at 10:07 AM ET, we experienced an elevated rate of memory-related errors impacting evaluations running through JQ input attributes. As a result, some evaluations returned a null value for the input attribute instead of the correct value, potentially interrupting decisioning in the Workflow. Impacted applications would need to be re-run. Only workflows using input attributes with JQ were impacted; other Workflow logic was not impacted. The issue has been identified and resolved, and all systems are now operating normally.

The root cause has been identified. Response times for the Dashboard and API have returned to normal levels since 3:46 PM ET.

Between 11:20 AM and 12:04 PM ET, some workflows returned a 500 error when attempting to save a new version. Existing workflow versions and decisioning on existing workflow versions were not impacted. Once the root cause was identified as a previous code change, the issue was resolved at 12:04 PM ET when the affected change was rolled back, and all functionality related to workflow version saving was fully restored.

A fix has been implemented and all systems are operational.

The OpenCorporates team has assisted in resolving the issue, and the OpenCorporates data service is now fully operational. Any applications that previously failed due to this incident can now be re-run.

Alloy is observing error rates have decreased across all impacted services as of 9:36 AM ET. CloudFlare has confirmed a fix has been implemented as of 9:42 AM ET. More information about the CloudFlare outage can be found here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Our monitoring confirms that processing has returned to normal. We have not observed any further errors since 12:20 PM ET. Any applications that failed during this period can now be re-run successfully.

Our monitoring confirms that processing has returned to normal. We have not observed any timeout errors since 6:02 PM ET. Any applications that failed during this period can now be re-run successfully.