Expel の障害履歴

1. 2026年9月22日 15:26 UTCinvestigating

   10:30AM ETでは、アラートの摂取に問題が起き始めました。 SOC の動作は影響されますが、サービスが復元されると、データが失われることはありません。 誠に勝手ながら12時30分より順次アップデートを致します.

2. 2026年9月22日 16:21 UTCinvestigating

   10:30AM ETでは、アラートの摂取に問題が起き始めました。 SOC の動作は影響されますが、サービスが復元されると、データが失われることはありません。 1:30PM ETにてアップデートを行います.

3. 2026年9月22日 17:28 UTCinvestigating

   10:30AM ETでは、アラートの摂取に問題が起き始めました。 SOC の動作は影響されますが、サービスが復元されると、データが失われることはありません。 2:30PM ETにてアップデートを行います.

4. 2026年9月22日 18:24 UTCinvestigating

   10:30AM ETでは、アラートの摂取に問題が起き始めました。 SOC の動作は影響されますが、サービスが復元されると、データが失われることはありません。 3:30PM ETにてアップデートを行います.

5. 2026年9月22日 19:13 UTCmonitoring

   修正を実装し、その事件を解決すべきだと確信しています。 インフラの健全性を監視し、問題がなければ解決します。 何か問題が起きているかご確認ください.

6. 2026年9月22日 21:03 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月30日 9:43 UTCidentified

   ワークベンチからのメールは、午前12時以降に遅延します。 根本原因を特定し、是正に努めます。 結果の応答をフィッシング, ユーザーメール通知, Org-Levelメールのチケット通知は、午前12時以降遅延します. SOCの動作やアラートの摂取は影響しません。 UTCの12時30分までにアップデートを致します

2. 2026年8月30日 11:10 UTCidentified

   私たちは、原因が是正に取り組んでいることを確認しました。 また、疑わしいフィッシングメールを提出する際に、この問題により、メールがWorkbenchにレビューが届かないことを確認しました。 1pm UTCのアップデート.

3. 2026年8月30日 12:58 UTCidentified

   これからも、これからもよろしくお願い申し上げます。 MDRサービスは不備です。 アラートの摂取、検出、調査が正常に動作しています。 Slack、Microsoft Teams、PagerDuty、Opsgenie、Service Nowの通知はまだ配信されます。 Workbenchからのメール配信は利用できません。 現時点ではアクションは必要ありません。サービスが復元されると、フィッシング投稿の返金手順が確認されます。 次のアップデート: 8月31日(月)13:00 UTC(9:00 AM ET)

4. 2026年8月30日 18:14 UTCmonitoring

   Workbench からのメール配信は現在、キュー内のメールが再生されています。 再生が完了すると更新が投稿されます.

5. 2026年8月30日 19:53 UTCresolved

   この問題は解決されます。 Workbenchからのメール配信は復元され、フィッシングメールの送信は正常に処理されます。 現時点で提出されたフィッシングメールは、Expel が受信されず、処理できませんでした。 この期間中に報告した内容を再送信してください。 今回生成した通知メールが届きました。 元々生成されたタイムスタンプよりも後で到着する場合があります.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月17日 2:21 UTCinvestigating

   9:58pm EDT では、Workbench へのアクセスを防止する Workbench データベースの問題が発生しました。 11pm EDT によるアップデートを行います.

2. 2026年7月17日 2:34 UTCmonitoring

   修正を実装し、その事件を解決すべきだと確信しています。 インフラの健全性を監視し、問題がなければ解決します。 何か問題が起きているかご確認ください.

3. 2026年7月17日 3:01 UTCresolved

   インシデントが解決し、すべてのシステムが再び利用可能になりました。 顧客データが失われず、SOCの運用に影響が及ぶが、正常に戻りました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月13日 20:20 UTCinvestigating

   6月18日、ベンダーのアラートをサイレントにインデックスしたロジックを意図的に導入した Expel の環境で変更を行いました。 この変更は、7月1日に識別された直後にアラートを復元するために再変換されました。 当社のチームは、当社が再生している顧客の環境の数内で、影響を受けたサービス期間中に発生したいくつかのアラートを識別しました。 万が一の事態が生じた場合は、Workbench 経由でお客様に影響を受けたお客様は通知されます。 その際は、お気軽にお問い合わせ下さい.

2. 2026年8月12日 17:47 UTCresolved

   This incident has been resolved.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月18日 20:37 UTCinvestigating

   At 2pm ET, we began experiencing a problem with our notification system that is causing notification delays to our customers. We will provide an update by 5pm ET.

2. 2026年6月18日 21:05 UTCidentified

   We've identified the cause of the delayed notifications as an issue with a third-party notification vendor. A fix is currently being applied. Workbench notifications have been delayed since 19:09 UTC, and we'll provide another update at 21:30 UTC.

3. 2026年6月18日 21:35 UTCidentified

   Workbench notifications continue to be delayed since 19:09 UTC due to an issue with a third-party notification vendor. They are working on a fix. All delayed notifications will be processed once the outage is resolved. Next update 22:00 UTC

4. 2026年6月18日 22:13 UTCmonitoring

   The cause of the notification delays has been resolved and we are observing delayed messages being delivered. All delayed notifications will be processed and we will continue to monitor.

5. 2026年6月18日 23:28 UTCresolved

   All delayed messages have been delivered and the notifications system is fully operational.

1. 2026年6月17日 23:11 UTCinvestigating

   We are investigating an issue affecting the processing of phishing submissions. Beginning at 19:47 UTC, phishing submissions are not being processed, which is preventing the creation of Phishing Expel Alerts. Suspected phishing emails submitted for review during this period may not yet be analyzed. Our team is actively working to identify the cause. We will provide an update by 00:00 UTC.

2. 2026年6月18日 0:07 UTCinvestigating

   We are continuing to investigate this issue

3. 2026年6月18日 0:59 UTCinvestigating

   We are continuing to investigate this issue. Will post another update in 60 minutes.

4. 2026年6月18日 2:12 UTCinvestigating

   We think we have identified the problem and are working on a resolution right now. Will update again in 60 minutes.

5. 2026年6月18日 3:17 UTCinvestigating

   Beginning at 19:47 UTC, phishing submissions are not being processed, which is preventing the creation of Phishing Expel Alerts. Suspected phishing emails submitted for review during this period may not yet be analyzed. We've identified the cause and we are working with the vendor to address the issue. We expect to retrieve and process them once service is restored.

6. 2026年6月18日 13:29 UTCresolved

   This incident has been resolved.

1. 2026年6月17日 16:16 UTCinvestigating

   At 10am ET, we began experiencing a problem with alert ingestion for some AWS Cloudtrail devices. We will provide an update by 1pm ET.

2. 2026年6月17日 16:37 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年6月17日 16:59 UTCresolved

   This incident has been resolved.

1. 2026年6月9日 15:40 UTCinvestigating

   Workbench is currently experiencing connectivity issues and may be inaccessible for some users. We are investigating the issue and will provide an update within an hour.

2. 2026年6月9日 16:42 UTCinvestigating

   Workbench is still experiencing connectivity issues. We are still investigating the issue and will provide an update in 1 hour.

3. 2026年6月9日 17:22 UTCmonitoring

   We have identified the issue, have rolled out a fix and are monitoring the situation.

4. 2026年6月9日 17:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026年6月9日 17:33 UTCresolved

   This incident has been resolved.

1. 2026年5月13日 16:23 UTCidentified

   We are aware of an issue with the Expel Alerts count being inflated for customers. We have identified the root cause and are working on a remediation. SOC operations and alert ingestion are not affected. We will provide another update by 1pm EDT.

2. 2026年5月13日 16:38 UTCidentified

   We have remediated the issue with Expel Alerts count being inflated for customers by shifting to a different source of statistics. We are working on fixing the underlying issue with our main source of count data. We will provide another update by 1pm EDT.

3. 2026年5月13日 16:46 UTCresolved

   The incident has been resolved, and all alerts counts are once again accurate. No customer data was lost, and SOC operations were not impacted.

1. 2026年5月1日 18:50 UTCinvestigating

   At 2pm EDT, we began experiencing a problem with the customer device secrets service that is preventing our infrastructure from accessing customer security devices. We will provide an update by 3:30pm EDT.

2. 2026年5月1日 19:09 UTCmonitoring

   We have implemented a fix and believe the incident to be resolved. We are seeing customer security devices returning to healthy status. We are monitoring the health of the infrastructure and will post another update by 4pm EDT.

3. 2026年5月1日 20:01 UTCresolved

   The incident has been resolved, and all systems are once again fully available. No customer data was lost, and all previously-accessible security devices are once again accessible and ingesting alerts.

1. 2026年4月25日 17:42 UTCinvestigating

   At 1pm ET, we began experiencing a problem with our notification system that is causing notification delays to our customers.  We will provide an update by 2:30pm ET.

2. 2026年4月25日 18:09 UTCresolved

   This issue has been resolved. All notifications in the backlog have been delivered and new notifications are being delivered as normal.

1. 2026年4月20日 16:20 UTCinvestigating

   At 10:59AM EDT, we noticed that a set of devices have been unhealthy since last week due to invalid credentials. We believe the cause to be a change to our device credentials storage subsystem. We are working to identify the specific set of devices and restore the credentials. Once restored, all delayed alerts will be ingested. We will provide an updated by 1pm EDT.

2. 2026年4月20日 17:00 UTCinvestigating

   We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 1:30pm EDT.

3. 2026年4月20日 17:35 UTCinvestigating

   We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 2:00pm EDT.

4. 2026年4月20日 18:01 UTCinvestigating

   We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 2:30pm EDT.

5. 2026年4月20日 18:34 UTCidentified

   We have restored the credentials for the affected subset of devices. We are monitoring closely to ensure proper ingestion of delayed alerts. We will provide another update by 3:00pm EDT.

6. 2026年4月20日 19:02 UTCidentified

   We have restored the credentials for the subset of devices. We are monitoring closely to ensure proper ingestion of delayed alerts. We will provide another update by 3:30pm EDT.

7. 2026年4月20日 19:34 UTCmonitoring

   We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We are investigating the remaining unhealthy devices, which do not seem related to the credentials. We will provide another update by 4:00pm EDT.

8. 2026年4月20日 20:01 UTCmonitoring

   We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We are investigating the remaining unhealthy devices, which do not seem related to credentials. We will provide another update by 4:30pm EDT.

9. 2026年4月20日 20:54 UTCresolved

   We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We investigated the remaining unhealthy devices, which are not related to the customer secrets vault upgrade. This incident is resolved.

1. 2026年3月24日 16:58 UTCinvestigating

   Notifications are currently not being delivered to Microsoft Teams since 4pm UTC. We are actively investigating to determine and address the root cause. We advise you login to Workbench for timely updates and/or to engage with Expel's SOC until the issue is resolved. Updates will be shared as soon as they are available. We will provide an update by 5:30pm UTC.

2. 2026年3月24日 17:49 UTCidentified

   Update: We have confirmed there are no technical issues with Workbench or with our third party systems that support notifications. Microsoft has since updated its Teams service health to indicate they are investigating a possible issue. We recommend you check your MSFT 365 service health and Microsoft's status page for updates: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect Until further notice, please continue to login to Workbench for timely updates and/or to engage with Expel's SOC. We will provide notice when Workbench notifications to Teams are operational.

3. 2026年3月24日 21:02 UTCmonitoring

   Update: We are observing a broad recovery in MS Teams message delivery as of 19:10 UTC. However, Microsoft has confirmed that service remains degraded for some users in the West United States region due to ongoing infrastructure optimizations. We are continuing to monitor the situation. Any messages delayed during this incident are being automatically reprocessed for delivery.

4. 2026年3月24日 21:12 UTCresolved

   Resolved: Microsoft has confirmed that the issues affecting Teams bots and message delivery are now fully resolved. All delayed messages have been reprocessed and delivered. Service is operating normally.

1. 2026年3月2日 18:35 UTCmonitoring

   We are currently monitoring an outage affecting the AWS GuardDuty service. As a result of this outage, our integration with AWS GuardDuty is currently reporting as unhealthy. We will provide an update within 60 minutes, or as soon as more information is available.

2. 2026年3月2日 19:36 UTCmonitoring

   We are working on a workaround that will bypass the faulty AWS region in order resume alert ingestion from healthy regions. Once the outage in the faulty region is over, we will resume ingestion in that region. We will provide an update within 60 minutes, or as soon as more information is available.

3. 2026年3月2日 20:36 UTCresolved

   Workaround is in place, we are bypassing the faulty AWS region and all impacted devices have resumed ingestion. Once the outage in the faulty region is over, we will resume ingestion in that region. Alert Ingestion issue resolved.

1. 2026年2月2日 21:00 UTCinvestigating

   Expel is investigating an issue with Workbench notifications that may be preventing users from receiving outbound notifications from Workbench to User Email, Email Ticketing, Slack, MS Teams, PagerDuty, and OpsGenie integrations since 19:30 UTC. We will provide an update by 21:30 UTC.

2. 2026年2月2日 21:15 UTCidentified

   We have identified the root cause as an issue with a 3rd party vendor. They are actively working on resolving the issue. We have confirmed that outbound notifications from Workbench have not been delivered to to User Email, Email Ticketing, Slack, MS Teams, PagerDuty, and OpsGenie since 19:30 UTC. These notifications are queued and will be re-sent when the issue is resolved. Alert ingestion is not affected. We will provide another update by 21:30 UTC.

3. 2026年2月2日 21:41 UTCidentified

   Outbound notifications from Workbench to User Email, Email Ticketing, Slack, MS Teams, PagerDuty, and OpsGenie continue to be delayed. We will provide an update by 22:00 UTC.

4. 2026年2月2日 22:00 UTCidentified

   Outbound notifications from Workbench to User Email, Email Ticketing, Slack, MS Teams, PagerDuty, and OpsGenie continue to be delayed. We will provide an update by 22:30 UTC.

5. 2026年2月2日 22:12 UTCmonitoring

   We are observing that delayed messages are starting to be delivered. We will monitor the backlog of delayed notifications and the health of the system. We will provide an update by 22:30 UTC.

6. 2026年2月2日 22:33 UTCresolved

   The incident has been resolved, and all delayed notifications have been delivered. No customer data was lost, and SOC operations were not impacted.

1. 2026年1月20日 20:31 UTCinvestigating

   At 3:00pm ET, we began experiencing a problem with alert ingestion. We will provide an update by 4:30pm ET.

2. 2026年1月20日 20:54 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年1月20日 23:02 UTCresolved

   This incident has been resolved.

1. 2026年1月7日 19:51 UTCinvestigating

   Starting 1/6/25 at roughly 12:00 EST, we have identified an issue with our phishing service where outcome emails are being sent multiple times to some users and are investigating the root cause. Ingestion and email review are not affected. We will provide an update at 4pm EST.

2. 2026年1月7日 21:11 UTCidentified

   We believe we have identified the root cause of duplicate phishing outcome emails and are preparing a hotfix. Next update at 5pm EST.

3. 2026年1月7日 22:00 UTCmonitoring

   The hotfix for duplicate phishing outcomes has been deployed and we are monitoring. Next update at 6pm EST.

4. 2026年1月7日 22:54 UTCresolved

   The hotfix for phishing submission outcome emails was successful and behavior has returned to normal. This incident is resolved.

1. 2025年12月29日 21:26 UTCinvestigating

   At 3:17, we began experiencing a problem with enrichment service that is impacting detections. We will provide an update by 4:45.

2. 2025年12月29日 21:49 UTCmonitoring

   We have identified and implemented a fix and are monitoring; service queues are approaching normal.

3. 2025年12月29日 22:09 UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. 2025年11月18日 15:34 UTCidentified

   Workbench cannot currently deliver notifications to Microsoft Teams. The issue began around 9:45am ET. Expel is actively investigating the issue to determine if it is related to the larger Cloudflare outage. We recommend you utilize email notifications in the interim, and can confirm communicating with Expel personnel via Microsoft Teams still works. The issue is specific to Workbench notifications.

2. 2025年11月18日 15:50 UTCmonitoring

   The underlying issue has been resolved We are monitoring the health of the infrastructure and will resolve this if there are no outstanding issues. Please let us know if you are experiencing any problems.

3. 2025年11月19日 18:17 UTCresolved

   This incident has been resolved.

1. 2025年11月12日 15:28 UTCidentified

   We’re upgrading our API connection and that may impact delivery of some alerts to Workbench. We are actively investigating and collaborating on a solution to ensure the consistent and complete delivery of all alert data. Please reach out to Orca if you’d like additional information. Thank you for your patience and understanding as we work through this.

2. 2026年4月17日 13:52 UTCresolved

   This incident has been resolved.