57 Alloy incidents · Gouere 2024 — official updates, affected components, duration and resolution details.
A funcionalidade de exportação tem experimentado desempenho degradado ao longo desta semana; estamos investigando o problema. Estamos actualmente a investigar esta questão.
Identificamos o problema, implantamos uma correção e confirmamos que o desempenho do processamento de exportação retornou aos níveis normais.
Traduzido automaticamente da atualização oficial do incidente.
Entre 12:45 PM e 1:20 PM ET em 27 de agosto, um fornecedor de dados de terceiros Threatmetrix experimentou uma interrupção de serviço que causou erros intermitentes de conexão em verificações de inteligência de dispositivo. Durante esta janela, algumas avaliações que utilizam o serviço impactado completaram-se como parciais em vez de retornarem uma resposta completa do provedor, e algumas solicitações viram latências elevadas ou tempo limite de conectores. O provedor confirmou que o problema subjacente está resolvido, e as taxas de erro voltaram ao normal até 1:20 PM ET. As avaliações realizadas fora desta janela não foram afetadas.
Traduzido automaticamente da atualização oficial do incidente.
Nossa automação detectou desempenho degradado dos componentes Dashboard, API de produção e Sandbox API. Estamos actualmente a investigar esta questão.
O desempenho foi restaurado, todos os componentes estão operacionais.
A questão foi totalmente resolvida. Taxas de erro elevadas foram observadas em 25 de agosto entre 14:18 e 14:22 ET e entre 14:29 e 14:35 ET
Traduzido automaticamente da atualização oficial do incidente.
Detectamos problemas com o nosso fornecedor de formatação de endereços. A decisão continua a funcionar, mas o endereço fornecido em bruto será enviado para serviços a jusante, o que pode resultar em alguns falsos negativos. Estamos em contato com o fornecedor e atualizaremos assim que soubermos mais.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do incidente.
Alguns clientes estão tendo taxas de erro elevadas para a nossa API Journeys. Estamos a investigar o impacto e a trabalhar na reparação.
Impusemos uma solução fixa que resolveu a maioria das questões, estamos actualmente a acompanhar
A questão foi agora resolvida e a nossa equipa continua a acompanhar. Também confirmamos que este caso afetou nosso painel, e que o impacto relacionado também foi abordado.
O tráfego vivo foi totalmente restaurado e a questão subjacente foi resolvida. Continuamos a abordar a latência residual que afeta a indexação do painel para solicitações submetidas durante o período de incidente, e a equipe está trabalhando ativamente para recuperação total.
O problema que afeta a API Journeys foi totalmente resolvido e o serviço voltou ao normal. Nós completamos o monitoramento e confirmamos que a funcionalidade relacionada do painel também se recuperou a partir de 21 de julho de 2026 às 5:11 PM ET. Obrigado pela sua paciência enquanto trabalhávamos para restaurar o serviço.
Traduzido automaticamente da atualização oficial do incidente.
Atualmente estamos investigando relatórios de problemas de login e filas de aplicativos não exibidas para alguns clientes. Nossa equipe está trabalhando ativamente para identificar a causa e fornecerá outra atualização assim que mais informações estiverem disponíveis.
Confirmamos que a funcionalidade de login e as Filas de Aplicação retornaram à operação normal, e nenhum impacto adicional está sendo observado. Obrigado pela vossa paciência enquanto trabalhávamos para resolver esta questão.
Traduzido automaticamente da atualização oficial do incidente.
Nosso monitoramento detectou falhas elevadas nos serviços da LexisNexis, e nossa equipe de engenharia está investigando ativamente. Nós forneceremos uma atualização assim que mais informações estiverem disponíveis.
Confirmamos que as elevadas taxas de erro são devidas a uma falha que afecta os serviços LexisNexis. Actualmente, confirmam-se os seguintes serviços: InstantID Compliance Mundial RiskView LexisNexis Inteligência de Fraude 2 Accurint InstantIDQA Pesquisa Pessoal Melhorada Contatamos a LexisNexis e aguardamos uma atualização na linha do tempo estimada para restauração de serviços. Continuaremos a monitorar a situação e fornecer atualizações à medida que recebemos informações adicionais.
Estamos vendo taxas de erro diminuirem nos serviços da LexisNexis impactados. Além disso, a página de status LexisNexis, anteriormente inacessível durante o incidente, está novamente disponível - https://status.lexisnexisrisk.com/. Continuaremos a monitorar de perto o desempenho e forneceremos outra atualização quando tivermos confirmado que as taxas de erro retornaram totalmente ao normal.
Continuamos a ver a recuperação através dos serviços da LexisNexis impactados, com a maioria dos serviços agora funcionando normalmente. Ainda estamos observando taxas de erro elevadas para RiskView e InstantVerify International e estamos continuando a monitorar esses serviços de perto. Forneceremos outra atualização depois de termos confirmado que todos os serviços foram totalmente recuperados.
Vimos a recuperação através dos serviços da LexisNexis impactados e as taxas de erro retornaram aos níveis esperados. Este incidente é agora considerado resolvido. Continuaremos a trabalhar com a equipe LexisNexis para obter uma Análise de Causas Root (RCA). Se você gostaria de receber uma cópia da RCA quando estiver disponível, entre em contato com [email protected].
Traduzido automaticamente da atualização oficial do incidente.
Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.
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.
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.
After further montioring, we have not observed any new errors. All systems are operating normally.
Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.
Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.
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.
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're currently investigating a period of latency and intermittent API unavailability that occurred between 11 and 11:15 ET.
We believe the cause of the latency is resolved.
Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.
The impact is limited to a subset of test suite endpoints used by the dashboard, our production apis were not impacted.
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.
Our API integration tests have encountered an increase in errors. We are currently investigating. Stay tuned for updates.
API functionality has been fully restored. We are continuing to investigate the impact and look into root causes.
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.
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 [email protected] 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.
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 [email protected] 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.
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.
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.
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.
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.
We are still investigating this issue and will provide another update as soon as more information is available.
A fix has been implemented and all systems are operational.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.