57 incidente Alloy înregistrate începând din iulie 2024, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
Funcţionalitatea exporturilor a cunoscut performanţe degradate pe parcursul acestei săptămâni; noi investigăm problema. În prezent investigăm această problemă.
Am identificat problema, am implementat un fix, și a confirmat performanța de prelucrare a exporturilor a revenit la niveluri normale.
Traducere automată din actualizarea oficială a incidentului.
Între orele 12:45 PM și 1:20 PM ET la 27 august, un furnizor de date terț a suferit o perturbare a serviciului care a cauzat erori intermitente de conectare la verificările de informații ale dispozitivului. În timpul acestei ferestre, unele evaluări care utilizează serviciul cu impact au fost completate ca fiind parțiale, în loc să returneze un răspuns complet al furnizorului, iar unele cereri au înregistrat întârzieri ridicate latente sau conectori. Furnizorul a confirmat că problema de bază este rezolvată, iar ratele de eroare au revenit la normal până la 1:20 PM ET. Evaluările prezentate în afara acestei ferestre nu au fost afectate.
Traducere automată din actualizarea oficială a incidentului.
Automatizarea noastra a detectat performanta degradata a componentelor Dashboard, Production API si Sandbox API. În prezent investigăm această problemă.
Performanţa a fost restabilită, toate componentele sunt operaţionale.
Problema a fost rezolvată pe deplin. Ratele ridicate de eroare au fost observate pe 25 august între 14:18 şi 14:22 PM ET şi între 14:29 şi 14:35 PM ET
Traducere automată din actualizarea oficială a incidentului.
Am detectat probleme cu furnizorul de adrese. Decizia continuă să funcţioneze, însă adresa brută va fi trimisă serviciilor din aval, ceea ce poate duce la unele fals negative. Suntem în prezent în contact cu vânzătorul și va actualiza de îndată ce vom ști mai multe.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
Unii clienți se confruntă cu rate ridicate de eroare pentru API noastre Călătorii. Investigăm impactul acum şi lucrăm la remediere.
Am împins un fix care a rezolvat majoritatea problemelor, în prezent monitorizăm
Problema a fost rezolvată acum, iar echipa noastră încă monitorizează. Am confirmat, de asemenea, că acest caz a afectat tabloul nostru de bord, și că impactul aferent a fost abordat, de asemenea.
Traficul live a fost restabilit complet, iar problema de bază a fost rezolvată. Continuăm să abordăm latența reziduală care afectează indexarea tabloului de bord pentru cererile depuse în timpul perioadei de incident, iar echipa lucrează în mod activ pentru recuperarea completă.
Problema care afectează Journeys API a fost pe deplin rezolvată, iar serviciul a revenit la normal. Am finalizat monitorizarea şi am confirmat că funcţionalitatea tabloului de bord aferent şi-a revenit la 21 iulie 2026 la ora 5:11 PM ET. Vă mulțumim pentru răbdare în timp ce am lucrat pentru a restabili serviciul.
Traducere automată din actualizarea oficială a incidentului.
Investigăm în prezent rapoarte de probleme de conectare și Queues aplicație nu afișare pentru unii clienți. Echipa noastră lucrează activ pentru a identifica cauza și va oferi o altă actualizare de îndată ce mai multe informații sunt disponibile.
Am confirmat că funcționalitatea de autentificare și Queues Aplication au revenit la funcționarea normală, și nu se observă niciun impact suplimentar. Vă mulțumim pentru răbdare în timp ce am lucrat pentru a rezolva această problemă.
Traducere automată din actualizarea oficială a incidentului.
Monitorizarea noastră a detectat eșecuri ridicate pentru serviciile LexisNexis, iar echipa noastră de inginerie investighează activ. Vom oferi o actualizare de îndată ce mai multe informații sunt disponibile.
Am confirmat că ratele ridicate de eroare se datorează unei întreruperi care afectează serviciile LexisNexis. În prezent, se confirmă impactul următoarelor servicii: InstantID Complianţă mondială RiskView LexisNexis Fraud Intelligence 2 Acuratețe InstantIDQA Description Am contactat LexisNexis și așteptăm o actualizare a calendarului estimat pentru restaurarea serviciului. Vom continua să monitorizăm situația și să oferim actualizări în timp ce primim informații suplimentare.
Vedem scăderea ratelor de eroare în serviciile LexisNexis afectate. În plus, pagina de stare LexisNexis, care a fost anterior inaccesibilă în timpul incidentului, este acum disponibilă din nou - https://status.lexisnexisrisk.com/. Vom continua să monitorizăm îndeaproape performanța și vom furniza o altă actualizare odată ce vom confirma că ratele de eroare au revenit complet la normal.
Continuăm să vedem redresarea în cadrul serviciilor LexisNexis afectate, majoritatea serviciilor funcţionând în mod normal. Încă observăm rate ridicate de eroare pentru RiskView și InstantVerify International și continuăm să monitorizăm îndeaproape aceste servicii. Vom furniza o altă actualizare după ce vom confirma că toate serviciile s-au recuperat complet.
Am văzut o recuperare a serviciilor LexisNexis afectate, iar ratele de eroare au revenit la nivelurile preconizate. Acest incident este acum considerat rezolvat. Vom continua să lucrăm cu echipa LexisNexis pentru a obține o analiză Root Cause (RCA). Dacă doriți să primiți o copie a RCA atunci când acesta devine disponibil, vă rugăm să contactați [email protected].
Traducere automată din actualizarea oficială a incidentului.
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.