57 Alloy incidents · juli 2024 — official updates, affected components, duration and resolution details.
Eksport funktionalitet har oplevet forringet ydeevne i hele denne uge; vi undersøger problemet. Vi undersøger i øjeblikket dette spørgsmål.
Vi har identificeret problemet, indsat en rettelse, og bekræftet eksport behandling ydeevne er vendt tilbage til normale niveauer.
Automatisk oversat fra den officielle hændelsesopdatering.
Mellem 12: 45 PM og 1: 20 PM ET den 27. august, en tredjeparts dataudbyder Threatmetrix oplevede en service afbrydelse, der forårsagede intermitterende forbindelse fejl på enheden intelligens kontrol. I dette vindue, nogle evalueringer, der bruger påvirket service afsluttet som delvis snarere end at returnere en fuld udbyder svar, og nogle anmodninger så forhøjet latency eller stik timeouts. Udbyderen har bekræftet den underliggende problem er løst, og fejlrater returneres til normal med 1: 20 PM ET. De vurderinger, der blev fremlagt uden for dette vindue, blev ikke påvirket.
Automatisk oversat fra den officielle hændelsesopdatering.
Vores automatisering opdaget forringet ydeevne Dashboard, Produktion API og Sandbox API komponenter. Vi undersøger i øjeblikket dette spørgsmål.
Præstationen er genoprettet, alle komponenter er i drift.
Spørgsmålet er løst. Der blev observeret forhøjede fejlrater den 25. august mellem 14: 18 og 14: 22 ET og mellem 14: 29 og 14: 35 ET
Automatisk oversat fra den officielle hændelsesopdatering.
Vi har opdaget problemer med vores adresseformateringsudbyder. Beslutningen fortsætter med at fungere, men råadresse vil blive sendt til downstream-tjenester, hvilket kan resultere i nogle falske negativer. Vi er i øjeblikket i kontakt med sælgeren og vil opdatere, så snart vi ved mere.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Nogle kunder oplever forhøjede fejlrater for vores rejsemål API. Vi undersøger virkningen nu og arbejder på oprydning.
Vi har presset på for at få en fast ordning, som har løst størstedelen af problemerne, vi overvåger i øjeblikket
Spørgsmålet er nu løst, og vores hold overvåger stadig. Vi har også bekræftet, at denne sag påvirkede vores instrumentbræt, og at relateret indvirkning også er blevet behandlet.
Live trafik er blevet fuldt genoprettet, og det underliggende problem er blevet løst. Vi fortsætter med at behandle resterende latency påvirker dashboard indeksering for anmodninger indgivet i hændelsesperioden, og holdet arbejder aktivt mod fuld inddrivelse.
Spørgsmålet om rejserne API er blevet helt løst, og service er vendt tilbage til normal. Vi har afsluttet overvågning og bekræftet, at relateret dashboard funktionalitet har også genvundet fra juli 21, 2026 på 5: 11 PM ET. Tak for din tålmodighed, mens vi arbejdede for at genoprette tjenesten.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er i øjeblikket ved at undersøge rapporter om login problemer og ansøgning køer ikke vise for nogle kunder. Vores team arbejder aktivt på at identificere årsagen og vil give en anden opdatering, så snart mere information er tilgængelig.
Vi har bekræftet, at login funktionalitet og Application Queues er vendt tilbage til normal drift, og ingen yderligere effekt bliver observeret. Tak for Deres tålmodighed, mens vi arbejdede på at løse dette problem.
Automatisk oversat fra den officielle hændelsesopdatering.
Vores overvågning har opdaget forhøjede fejl for LixisNexis-tjenester, og vores ingeniørhold undersøger aktivt. Vi vil give en opdatering, så snart mere information er tilgængelig.
Vi har bekræftet, at de forhøjede fejlrater skyldes en afbrydelse, der påvirker LixNexis 'tjenester. Følgende tjenester er i øjeblikket bekræftet at blive påvirket: InstantID WorldCompliance RiskView LexixNexis Bedrageriefterretningstjeneste 2 Nøjagtighed InstantIDQA EnhancedPersonsøgning Vi har kontaktet Lixix Nexis og afventer en opdatering af deres estimerede tidslinje for service restaurering. Vi vil fortsat overvåge situationen og levere opdateringer, når vi modtager yderligere oplysninger.
Vi ser fejlprocenter falde på tværs af de påvirkede LixNexis-tjenester. Derudover er LexisNexis status side, som tidligere var utilgængelige under hændelsen, nu tilgængelig igen - https: / / status.lexisnixisk.com /. Vi vil fortsat overvåge ydeevnen nøje og vil give endnu en opdatering, når vi har bekræftet, at fejlprocenterne er vendt helt tilbage til det normale.
Vi fortsætter med at se bedring på tværs af de ramte LixNexis tjenester, med de fleste tjenester nu fungerer normalt. Vi observerer stadig forhøjede fejlrater for RiskView og InstantVerify International og overvåger fortsat disse tjenester nøje. Vi vil give en anden opdatering, når vi har bekræftet, at alle tjenester er fuldt genvundet.
Vi har set bedring på tværs af de ramte LixNexis tjenester og fejlrater er vendt tilbage til forventede niveauer. Denne hændelse betragtes nu som løst. Vi vil fortsætte med at arbejde med Lixix Nexis holdet for at få en Root Case Analyse (RCA). Hvis du ønsker at modtage en kopi af RCA, når den bliver tilgængelig, bedes du kontakte support @ alloy.com.
Automatisk oversat fra den officielle hændelsesopdatering.
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.