Sep <var data-var='date'>10</var>, <var data-var='time'>20:37</var> EDT Resolved - The issue is currently resolved. Socure DocV is available again. RCA is upcoming. Sep <var data-var='date'>10</var>, <var data-var='time'>15:58</var> EDT Investigating - We are currently investigating the issue.

Socure DocV is failing to complete for multiple clients

Sep <var data-var='date'> 9</var>, <var data-var='time'>11:49</var> EDT Resolved - 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.

[Retroactive] Issues loading Workflows, Journeys, and Application Queues

Sep <var data-var='date'> 4</var>, <var data-var='time'>15:54</var> EDT Resolved - We’ve identified the issue, deployed a fix, and confirmed export processing performance has returned to normal levels. Sep <var data-var='date'> 4</var>, <var data-var='time'>15:10</var> EDT Investigating - Exports functionality has experienced degraded performance throughout this week; we’re investigating the issue. We are currently investigating this issue.

Degraded Export Functionality

Aug <var data-var='date'>27</var>, <var data-var='time'>12:45</var> EDT Resolved - 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.

Threatmetrix integration downtime

Aug <var data-var='date'>25</var>, <var data-var='time'>16:39</var> EDT Resolved - 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 Aug <var data-var='date'>25</var>, <var data-var='time'>14:56</var> EDT Monitoring - Performance have been restored, all components are operational. Aug <var data-var='date'>25</var>, <var data-var='time'>14:45</var> EDT Investigating - Our automation detected degraded performance of Dashboard, Production API and Sandbox API components. We are currently investigating this issue.

Degraded performance

Aug <var data-var='date'>20</var>, <var data-var='time'>16:43</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'>20</var>, <var data-var='time'>11:38</var> EDT Identified - We've detected issues with our address formatting provider.  Decisioning is continuing to operate, but raw provided address will be sent to downstream services, which may result in some false negatives. We are currently in contact with the vendor and will update as soon as we know more.

loqate down address formatter unavailable

Jul <var data-var='date'>22</var>, <var data-var='time'>11:44</var> EDT 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. Jul <var data-var='date'>21</var>, <var data-var='time'>14:52</var> EDT Update - Live traffic has been fully restored and the underlying issue has been resolved. We are continuing to address residual latency affecting dashboard indexing for requests submitted during the incident period, and the team is actively working toward full recovery. Jul <var data-var='date'>21</var>, <var data-var='time'>14:36</var> EDT Update - The issue has now been resolved, and our team is still currently monitoring. We've also confirmed that this case impacted our dashboard, and that related impact has been addressed as well. Jul <var data-var='date'>21</var>, <var data-var='time'>14:24</var> EDT Update - We have pushed a fixed which has resolved majority of the issues, we are currently monitoring Jul <var data-var='date'>21</var>, <var data-var='time'>13:56</var> EDT Investigating - Some customers are experiencing elevated error rates for our Journeys API. We are investigating the impact now, and working on remediation.

Journeys API Errors

Jul <var data-var='date'>17</var>, <var data-var='time'>10:51</var> EDT Resolved - 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. Jul <var data-var='date'>17</var>, <var data-var='time'>10:42</var> EDT Investigating - We are currently investigating reports of login issues and Application Queues not displaying for some customers. Our team is actively working to identify the cause and will provide another update as soon as more information is available.

Login Issues and Application Queues Not Displaying

Jul <var data-var='date'>14</var>, <var data-var='time'>15:09</var> EDT Resolved - 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 support@alloy.com. Jul <var data-var='date'>14</var>, <var data-var='time'>13:07</var> EDT Update - We are continuing to see recovery across the impacted LexisNexis services, with most services now operating normally. We are still observing elevated error rates for RiskView and InstantVerify International and are continuing to monitor those services closely. We will provide another update once we have confirmed that all services have fully recovered. Jul <var data-var='date'>14</var>, <var data-var='time'>12:31</var> EDT Monitoring - We are seeing error rates decrease across the impacted LexisNexis services. Additionally, the LexisNexis status page, which was previously inaccessible during the incident, is now available again - https://status.lexisnexisrisk.com/. We will continue to closely monitor performance and will provide another update once we have confirmed that error rates have fully returned to normal. Jul <var data-var='date'>14</var>, <var data-var='time'>11:53</var> EDT Identified - We have confirmed that the elevated error rates are due to an outage affecting LexisNexis services. The following services are currently confirmed to be impacted: InstantID WorldCompliance RiskView LexisNexis Fraud Intelligence 2 Accurint InstantIDQA EnhancedPersonSearch We have contacted LexisNexis and are awaiting an update on their estimated timeline for service restoration. We will continue to monitor the situation and provide updates as we receive additional information. Jul <var data-var='date'>14</var>, <var data-var='time'>11:31</var> EDT Investigating - Our monitoring has detected elevated failures for LexisNexis services, and our engineering team is actively investigating. We will provide an update as soon as more information is available.

Integration Downtime: LexisNexis

Jun <var data-var='date'>18</var>, <var data-var='time'>14:27</var> EDT Resolved - After further montioring, we have not observed any new errors. All systems are operating normally. Jun <var data-var='date'>18</var>, <var data-var='time'>14:19</var> EDT Monitoring - We are seeing recovery in dashboard performance with error rates returning toward normal levels. We are closely monitoring the platform to ensure stability is fully restored. Jun <var data-var='date'>18</var>, <var data-var='time'>14:15</var> EDT Update - We are currently investigating a spike in 500 errors affecting dashboard loading for some users . Our team is actively working to identify the root cause and mitigate the issue. We also observed a brief increase in API errors during this period, but API performance is now operating as expected. Jun <var data-var='date'>18</var>, <var data-var='time'>14:03</var> EDT Investigating - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.

API Downtime

Jun <var data-var='date'>11</var>, <var data-var='time'>15:56</var> EDT Resolved - Service has returned to normal operation as of 3:36 PM ET, and our monitoring confirms that API performance is stable. We will continue to monitor closely to ensure ongoing reliability. We apologize for any disruption this may have caused and appreciate your patience while we worked to resolve the issue. Jun <var data-var='date'>11</var>, <var data-var='time'>15:36</var> EDT Monitoring - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates. Jun <var data-var='date'>11</var>, <var data-var='time'>15:33</var> EDT Update - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates. Jun <var data-var='date'>11</var>, <var data-var='time'>15:22</var> EDT Investigating - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.

May <var data-var='date'> 8</var>, <var data-var='time'>09:00</var> EDT Resolved - 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.

[Retroactive] Homepage Dashboard Not Loading

May <var data-var='date'> 7</var>, <var data-var='time'>23:57</var> EDT Resolved - We believe the cause of the latency is resolved. May <var data-var='date'> 7</var>, <var data-var='time'>23:23</var> EDT Investigating - We're currently investigating a period of latency and intermittent API unavailability that occurred between 11 and 11:15 ET.

Latency and intermittent API unavailaiblity

Apr <var data-var='date'>23</var>, <var data-var='time'>11:33</var> EDT Resolved - The issue has been resolved. Apr <var data-var='date'>23</var>, <var data-var='time'>10:39</var> EDT Update - The impact is limited to a subset of test suite endpoints used by the dashboard, our production apis were not impacted. Apr <var data-var='date'>23</var>, <var data-var='time'>10:25</var> EDT Investigating - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.

Test Suite endpoints experiencing an increase in errors

Mar <var data-var='date'> 5</var>, <var data-var='time'>11:00</var> EST 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.

SDK Initialization Issue Affecting Some SDK Plugins

Mar <var data-var='date'> 4</var>, <var data-var='time'>23:00</var> EST Resolved - 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.

[Retroactive] Elevated JQ Evaluation Memory Errors

Mar <var data-var='date'> 3</var>, <var data-var='time'>04:30</var> EST Completed - The scheduled maintenance has been completed. Mar <var data-var='date'> 3</var>, <var data-var='time'>04:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>14</var>, <var data-var='time'>16:03</var> EST Scheduled - To enhance stability of our product, Alloy’s database will undergo a required upgrade on 03 March 2026 between 04:00 and 04:30 AM EST. During this time, you may experience brief API unavailability or increased errors. Please be sure to resend failed applications if you get a 206 or 5xx error message from us during the maintenance window. If you have additional questions regarding this scheduled maintenance, please contact us at support@alloy.com.

Database Maintenance

Feb <var data-var='date'>24</var>, <var data-var='time'>05:00</var> EST Resolved - API functionality has been fully restored. We are continuing to investigate the impact and look into root causes. Feb <var data-var='date'>24</var>, <var data-var='time'>04:30</var> EST Investigating - Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.

Feb <var data-var='date'>19</var>, <var data-var='time'>20:03</var> EST Resolved - Realtime webhook processing has been fully restored, and has maintained stability after monitoring. All new webhook events are now completing in realtime as expected. To further strengthen system stability, the engineering team has deployed an additional mitigation to prevent webhook queue backlogging under similar spike conditions. A thorough postmortem will be completed a Root Cause Analysis (RCA) can be shared with customers - please email support@alloy.com if you would like to receive the RCA. We are also investing in further improvements to the reliability and resiliency of our webhook queueing mechanism in the future to prevent event loss in the future. Please note, action is required to ensure applications process: During the incident, webhook events generated between 2:24 PM - 4:38 PM ET and 5:42 - 5:45 ET were not successfully processed and were permanently lost. Webhooks generated outside of this time window were not impacted. This issue affects applications that are stuck at a Journey step dependent on an Alloy webhook response to proceed (for example, action nodes), as well as applications that completed with a Manual Review outcome but are not reflecting back in core after review. Applications submitted during the affected window that are currently blocked due to a missing webhook dependency will need to be replayed. We recommend resubmitting those applications via API. Re-running an application will leverage cached data by default and will not trigger new calls to external data vendors. Feb <var data-var='date'>19</var>, <var data-var='time'>18:03</var> EST Monitoring - Realtime webhook processing has been fully restored. All new webhook events are now completing in realtime as expected. During the incident, webhook events generated between 2:24 PM - 4:38 PM ET and 5:42 - 5:45 ET were not successfully processed and were permanently lost. Webhooks generated outside of this time window were not impacted. This issue affects applications that are stuck at a Journey step dependent on an Alloy webhook response to proceed (for example, action nodes), as well as applications that completed with a Manual Review outcome but are not reflecting back in core after review. Applications submitted during the affected window that are currently blocked due to a missing webhook dependency will need to be replayed. We recommend resubmitting those applications via API. Re-running an application will leverage cached data by default and will not trigger new calls to external data vendors. A thorough postmortem will be completed a Root Cause Analysis (RCA) can be shared with customers - please email support@alloy.com if you would like to receive the RCA. We are also investing in further improvements to the reliability and resiliency of our webhook queueing mechanism in the future to prevent event loss in the future. Feb <var data-var='date'>19</var>, <var data-var='time'>15:49</var> EST Identified - We are currently experiencing delays in realtime webhook processing. The root cause has been identified and we are applying mitigation measures. We are now monitoring recovery as the processing queue returns to normal levels. Webhook events continue to be accepted; however, processing and delivery responses may be delayed until the existing backlog has been fully cleared.

Webhook Processing Delays

Feb <var data-var='date'>17</var>, <var data-var='time'>16:14</var> EST Resolved - The root cause has been identified. Response times for the Dashboard and API have returned to normal levels since 3:46 PM ET. Feb <var data-var='date'>17</var>, <var data-var='time'>16:03</var> EST Investigating - We are currently investigating reports of elevated response times that affect both the Alloy Dashboard and API. Some customers may experience slower load times for the dashboard and longer response times for the API. Our engineering team is actively investigating.

Increased Response Times for Dashboard and API

Feb <var data-var='date'> 2</var>, <var data-var='time'>12:27</var> EST Resolved - 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.

[Retroactive] Errors When Saving New Workflow Versions

Jan <var data-var='date'> 8</var>, <var data-var='time'>16:30</var> EST Resolved - A fix has been implemented and all systems are operational. Jan <var data-var='date'> 8</var>, <var data-var='time'>15:39</var> EST Update - We are still investigating this issue and will provide another update as soon as more information is available. Jan <var data-var='date'> 8</var>, <var data-var='time'>14:22</var> EST Update - Our team continues to investigate the issue. At this time, there is no new information to share, but we are actively working to identify the root cause and will share updates as soon as possible. Jan <var data-var='date'> 8</var>, <var data-var='time'>13:43</var> EST Investigating - We are currently investigating an issue where Journey Analytics pages, Investigation detail pages, Fraud Attack Radar, and some Evaluation detail pages may not be loading data as expected. The issue is intermittent, and not all pages are impacted. Decisioning is not impacted. Journey Applications and Evaluations are completing successfully.

Some Analytics and Detail Pages Not Loading Data

Jan <var data-var='date'> 2</var>, <var data-var='time'>17:05</var> EST Resolved - This incident has been resolved. Jan <var data-var='date'> 2</var>, <var data-var='time'>16:58</var> EST Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'> 2</var>, <var data-var='time'>16:15</var> EST Investigating - We are currently investigating an issue where Journey Analytics pages, Investigation detail pages, Fraud Attack Radar, and some Evaluation detail pages may not be loading data as expected. The issue is intermittent, and not all pages are impacted. Decisioning is not impacted. Journey Applications and Evaluations are completing successfully.

Dec <var data-var='date'> 3</var>, <var data-var='time'>17:51</var> EST Resolved - 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. Dec <var data-var='date'> 3</var>, <var data-var='time'>13:37</var> EST Investigating - Our monitoring has detected that calls to the OpenCorporates data integration are failing since Dec 2nd 4:52 PM ET. Requests are returning a 403 “Rate limit exceeded” error. We’re currently investigating and working with urgency with the OpenCorporates team to troubleshoot.

Integration Downtime: OpenCorporates

Nov <var data-var='date'>18</var>, <var data-var='time'>10:08</var> EST Resolved - 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 Nov <var data-var='date'>18</var>, <var data-var='time'>08:52</var> EST Update - Our monitoring has detected that the services Middesk, Iovation, Iovation Registration, and Zenwork Compliancely TIN Match are seeing full downtime due to a CloudFlare outage. We have reached out to the services for more information, and we are awaiting resolution from CloudFlare. We will periodically update the status page as we learn more. More information about the CloudFlare outage can be found here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 Nov <var data-var='date'>18</var>, <var data-var='time'>08:37</var> EST Investigating - A widespread Cloudflare outage is impacting multiple services, including Iovation and Middesk. We are monitoring the situation and investigating possible mitigation.

Is Alloy down?

Alloy status is UP

Lastest published events

Socure DocV is failing to complete for multiple clients

[Retroactive] Issues loading Workflows, Journeys, and Application Queues

Degraded Export Functionality

Alloy Services, Components and Regions

Recent Alloy events

Socure DocV is failing to complete for multiple clients

[Retroactive] Issues loading Workflows, Journeys, and Application Queues

Degraded Export Functionality

Threatmetrix integration downtime

Degraded performance

loqate down address formatter unavailable