退化的出口功能
Issues轻微事件
- investigating
出口功能在本周内表现不佳, 我们目前正在调查这一问题.
- resolved
我们已查明了问题.
自动翻译自官方事件更新。
57 Alloy incidents · 2024年7月 — official updates, affected components, duration and resolution details.
出口功能在本周内表现不佳, 我们目前正在调查这一问题.
我们已查明了问题.
自动翻译自官方事件更新。
8月27日12:45至1:20 PM ET之间,第三方数据提供商Preportmetrix经历了服务中断,导致设备智能检查出现间歇连接错误. 在这一窗口期间,一些使用受影响服务的评价是部分完成的,而不是返回提供者的完整答复,一些请求的延迟或连接器超时。 供应商确认基本问题已经解决,误差率于1:20 PM ET恢复正常. 在这个窗口外提交的评价没有受到影响.
自动翻译自官方事件更新。
我们的自动化检测到了Dashboard,Production API和Sandbox API组件的退化性能. 我们目前正在调查这一问题.
性能已经恢复,所有部件都投入使用.
问题已经完全解决。 8月25日14:18至14:22 PM ET之间和14:29至14:35 PM ET之间观察到了较高的出错率
自动翻译自官方事件更新。
我们发现地址格式化供应商有问题 决定仍在运作,但原始地址将送往下游服务,这可能导致一些虚假的负面反应。 我们目前正在与该供应商联系,并将在知道更多情况后立即更新.
这一事件已经得到解决.
自动翻译自官方事件更新。
有些顾客在我们的Journeys API上出现了较高的出错率. 我们正在调查影响,并致力于补救.
解决了大部分问题,我们正在监测
这个问题现已解决,我们的小组目前仍在监测。 我们还证实,这个案子影响了我们的仪表板, 相关的影响也得到了处理.
现场交通全面恢复,根本问题已经解决. 我们正在继续处理影响为事件期间提出的请求编制仪表板索引的剩余延迟问题,该小组正在积极努力争取全面恢复.
影响Journeys API的问题已完全解决,服务恢复正常. 我们已完成了监测,并确认,截至2026年7月21日,相关仪表板功能也在5:11 PM ET恢复. 谢谢你在努力恢复服务时的耐心.
自动翻译自官方事件更新。
我们正在调查关于登入问题和应用程序队列不为一些客户显示的报告。 我们的小组正在积极努力查明原因,一旦获得更多信息,我们将提供另一个最新情况.
我们确认,登录功能和应用程序队列已恢复正常运行,没有观察到进一步的影响。 谢谢你在我们努力解决这一问题期间的耐心.
自动翻译自官方事件更新。
我们的监控发现LexisNexis服务的失败率上升,我们的工程小组正在积极调查。 一旦获得更多信息,我们将立即提供最新情况.
我们确认,误差率高的原因是LexisNexis服务中断。 目前确认以下服务受到影响: 即时识别 世界遵约组织 风险核查 LexisNexis 欺诈情报 2 亚克锡 即时IDQA 增强个人搜索 我们已同LexisNexis联系,正在等待他们估计恢复服务的时间。 我们将继续监测局势,并在收到补充资料时提供最新情况.
我们看到受影响的LexisNexis服务的错误率下降。 此外,LexisNexis状态页面(在事件期间曾无法访问)现在又可以访问——https://status.lexisnexisk.com/。 我们将继续密切监测执行情况,一旦确认错误率已完全恢复正常,我们将再次提供最新情况.
我们继续看到受影响的LexisNexis服务恢复,大多数服务现在正常运行。 我们仍然观察到风险核查和即时核查国际的错误率较高,并继续密切监测这些服务。 一旦我们确认所有服务已完全恢复,我们将提供另一个最新情况.
我们看到受影响的LexisNexis服务的恢复,出错率已恢复到预期水平。 这一事件现在被认为得到解决。 我们将继续与LexisNexis团队合作,以获得根由分析。 如果您希望获得RCA的副本,请联系支持@alloy.com.
自动翻译自官方事件更新。
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.