分解された輸出機能性
Issues軽微なインシデント
- investigating
輸出機能性は、今週を通して劣化した性能を経験してきました。私たちは課題を調査しています。 現在、この問題を調査中です.
- resolved
問題を特定し、修正をデプロイし、エクスポート処理のパフォーマンスが正常レベルに戻りました.
公式のインシデント更新を自動翻訳しています。
57 Alloy incidents · 2024年7月 — official updates, affected components, duration and resolution details.
輸出機能性は、今週を通して劣化した性能を経験してきました。私たちは課題を調査しています。 現在、この問題を調査中です.
問題を特定し、修正をデプロイし、エクスポート処理のパフォーマンスが正常レベルに戻りました.
公式のインシデント更新を自動翻訳しています。
サードパーティのデータプロバイダであるThreatmetrixは、8月27日に12:45 PMと1:20 PM ETの間で、デバイスインテリジェンスチェックに断続的な接続エラーを引き起こしたサービス中断を経験しました。 このウィンドウでは、フルプロバイダーの応答を返すのではなく、部分的にインパクトのあるサービスを使用する評価がいくつかあります。また、一部のリクエストでは、高レイテンシやコネクタのタイムアウトが増加しました。 プロバイダーは、下書きの問題が解決され、エラー率は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 のエラー率が高くなります。 今のインパクトを調査し、是正に取り組んでいます.
問題の大部分を解決した固定をプッシュし、現在監視しています
問題が解決し、チームは現在監視中です。 また、このケースがダッシュボードに影響を及ぼし、その影響も対処されていることを確認しました.
ライブトラフィックは完全に復元され、根本的な問題が解決されました。 事件期間中に提出されたリクエストのダッシュボードのインデックス化に影響を及ぼす残留遅延に引き続き対処し、チーム全体で復旧に積極的に取り組んでいます.
ジャーニー API に影響する問題は完全に解決され、サービスは正常に戻りました。 2026年7月21日(水)午後5時11時11時11分に、関連するダッシュボード機能も回復したことを確認しました。 誠に有難うございます.
公式のインシデント更新を自動翻訳しています。
現在、一部のお客様にはログインの問題やアプリケーションキューのレポートを調査しています。 当社のチームは、原因を特定するために積極的に取り組んでおり、より多くの情報が利用可能になったらただちに別のアップデートを提供します.
ログイン機能とアプリケーションキューイングが正常な動作に戻ってきたことを確認し、さらなる影響が観察されていないことを確認しました。 この問題の解決に取り組んでいる間、あなたの忍耐をありがとう.
公式のインシデント更新を自動翻訳しています。
LexisNexisのサービスに対する高い失敗を監視し、エンジニアリングチームは積極的に調査しています。 最新情報を随時更新いたします.
LexisNexisサービスに影響する停電により、高い誤差率が確認されています。 現在、以下のようなサービスが影響を受けることが確認されています。 インスタントID ワールドコンプライアンス リスクビュー LexisNexis 詐欺インテリジェンス 2 アキュリン インスタントIDQA 強化パーソンサーチ LexisNexisに連絡し、サービスの復元のための推定タイムラインの更新を待っています。 今後も状況を監視し、追加情報を受け取るため、更新を行います.
LexisNexisのサービスに影響するエラー率が減少しています。 さらに、LexisNexisのステータスページは、以前にインシデント中にアクセス不能だったので、再び利用できます - https://status.lexisnexisrisk.com/。 今後もパフォーマンスをモニターし、エラー率が正常に戻ってきたことを確認した上で、別のアップデートを提供してまいります.
LexisNexis は、現在、ほとんどのサービスが正常に動作している、影響を受ける LexisNexis サービスの全体で回復を見続けています。 引き続き、リスクビューとInstantVerify Internationalの高値な誤差率を維持し、それらのサービスを密接に監視しています。 すべてのサービスが完全に回復していることを確認したら、別のアップデートを提供します.
LexisNexisのサービスやエラー率が予想されるレベルに返された影響を受けている間に回復しました。 この事件は解決されたと見なされます。 今後もLexisNexisチームと連携し、Root Cause Analysis(RCA)を取得していきます。 RCAのコピーを受け取りたい場合は、[email protected]までお問い合わせください.
公式のインシデント更新を自動翻訳しています。
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.