57 Alloy incidents · julio de 2024 — official updates, affected components, duration and resolution details.
La funcionalidad de las exportaciones ha experimentado un rendimiento degradado durante esta semana; estamos investigando el problema. Actualmente estamos investigando esta cuestión.
Hemos identificado la cuestión, implementado una solución, y el rendimiento de procesamiento de exportación confirmado ha regresado a niveles normales.
Traducido automáticamente desde la actualización oficial del incidente.
Entre las 12:45 PM y las 1:20 PM ET el 27 de agosto, un proveedor de datos de terceros Threatmetrix experimentó una interrupción del servicio que causó errores de conexión intermitente en los controles de inteligencia de dispositivos. Durante esta ventana, algunas evaluaciones que utilizan el servicio impactado completado como parcial en lugar de devolver una respuesta completa del proveedor, y algunas solicitudes vieron un tiempo elevado de latencia o de conexión. El proveedor ha confirmado que el problema subyacente se resuelve, y las tasas de error devueltos a la normalidad para 1:20 PM ET. Las evaluaciones presentadas fuera de esta ventana no se vieron afectadas.
Traducido automáticamente desde la actualización oficial del incidente.
Nuestra automatización detectó el rendimiento degradado de los componentes de Dashboard, Production API y Sandbox API. Actualmente estamos investigando esta cuestión.
Se han restaurado los resultados, todos los componentes están en funcionamiento.
La cuestión se ha resuelto totalmente. El 25 de agosto se observaron tasas de error elevadas entre las 14:18 y 14:22 PM ET y entre las 14:29 y 14:35 PM ET
Traducido automáticamente desde la actualización oficial del incidente.
Hemos detectado problemas con nuestro proveedor de formato de direcciones. La adopción de decisiones sigue funcionando, pero la dirección prestada se enviará a los servicios de abajo, lo que puede dar lugar a algunos falsos negativos. Actualmente estamos en contacto con el proveedor y actualizaremos tan pronto como sepamos más.
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Algunos clientes están experimentando tasas de error elevadas para nuestra API de viajes. Estamos investigando el impacto ahora, y trabajando en la rehabilitación.
Hemos empujado a un fijo que ha resuelto la mayoría de los problemas, estamos monitoreando actualmente
La cuestión ya se ha resuelto, y nuestro equipo sigue vigilando. También hemos confirmado que este caso impactó nuestro panel de control, y que también se ha abordado el impacto relacionado.
El tráfico en vivo ha sido totalmente restaurado y se ha resuelto la cuestión subyacente. Seguimos abordando la latencia residual que afecta a la indexación de tableros de datos para las solicitudes presentadas durante el período del incidente, y el equipo está trabajando activamente para la recuperación completa.
El problema que afecta a la API de viajes se ha resuelto completamente, y el servicio ha vuelto a la normalidad. Hemos completado el monitoreo y confirmado que la funcionalidad de panel de control relacionados también se ha recuperado a partir del 21 de julio de 2026 a las 5:11 PM ET. Gracias por su paciencia mientras trabajamos para restaurar el servicio.
Traducido automáticamente desde la actualización oficial del incidente.
Actualmente estamos investigando informes de problemas de inicio de sesión y solicitudes que no se muestran para algunos clientes. Nuestro equipo está trabajando activamente para identificar la causa y proporcionará otra actualización tan pronto como esté disponible más información.
Hemos confirmado que la funcionalidad de inicio de sesión y las colas de aplicación han regresado a la operación normal, y no se observa ningún impacto adicional. Gracias por su paciencia mientras trabajamos para resolver este problema.
Traducido automáticamente desde la actualización oficial del incidente.
Nuestro monitoreo ha detectado fallos elevados para los servicios de LexisNexis, y nuestro equipo de ingeniería está investigando activamente. Proporcionaremos una actualización tan pronto como esté disponible más información.
Hemos confirmado que las tasas de error elevadas se deben a un outage que afecta a los servicios de LexisNexis. Actualmente se confirman los siguientes servicios: InstantID WorldCompliance RiskView LexisNexis Fraud Intelligence 2 Accurint InstantIDQA EnhancedPersonSearch Hemos contactado a LexisNexis y estamos a la espera de una actualización de su plazo estimado para la restauración del servicio. Seguiremos vigilando la situación y proporcionando actualizaciones a medida que recibamos información adicional.
Estamos viendo disminuir las tasas de error en los servicios de LexisNexis impactados. Además, la página de estado de LexisNexis, anteriormente inaccesible durante el incidente, está disponible de nuevo - https://status.lexisnexisrisk.com/. Seguiremos monitoreando de cerca el rendimiento y proporcionaremos otra actualización una vez que hayamos confirmado que las tasas de error han vuelto a la normalidad.
Continuamos viendo la recuperación a través de los servicios de LexisNexis impactados, con la mayoría de los servicios que ahora funcionan normalmente. Todavía estamos observando tasas de error elevadas para RiskView y InstantVerify International y seguimos monitoreando esos servicios de cerca. Proporcionaremos otra actualización una vez que hayamos confirmado que todos los servicios se han recuperado completamente.
Hemos visto recuperación a través de los servicios de LexisNexis impactados y las tasas de error han regresado a los niveles esperados. Este incidente se considera resuelto. Seguiremos trabajando con el equipo de LexisNexis para obtener un Análisis de Causas Root (RCA). Si desea recibir una copia del RCA cuando esté disponible, comuníquese con [email protected].
Traducido automáticamente desde la actualización oficial del 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.