Histórico de interrupções do Expel

1. 30 Eost 2026 da 09:43 UTCidentified

   Os emails do Workbench estão atrasados desde as 12h UTC. Identificámos a causa da raiz e estamos a trabalhar numa reparação. Respostas de resultado de phishing, notificações de e-mail do usuário e notificações de ticketing de e-mail Org-Level são adiadas desde 12am UTC. As operações de SOC e a ingestão de alerta não são afetadas. Vamos fornecer outra atualização até 12:30 pm UTC

2. 30 Eost 2026 da 11:10 UTCidentified

   Identificámos que a causa continua a trabalhar na reparação. Também confirmamos que devido a este problema, quando alguém envia um e-mail suspeito de phishing, o e-mail não chegará ao Workbench para revisão. Próxima atualização às 13h UTC.

3. 30 Eost 2026 da 12:58 UTCidentified

   Continuamos a trabalhar na reparação. Os serviços MDR não são afectados. Alertar ingestão, detecção e investigação estão funcionando normalmente. Slack, Microsoft Teams, PagerDuty, Opsgenie e Service Now as notificações ainda estão sendo entregues. A entrega por e-mail da Workbench permanece indisponível. Nenhuma ação é necessária neste momento; vamos confirmar as etapas de resubmissão para submissões de phishing uma vez que o serviço é restaurado. Próxima atualização: Segunda-feira, 31 de agosto às 13:00 UTC (9:00 AM ET)

4. 30 Eost 2026 da 18:14 UTCmonitoring

   Entrega de e-mail do Workbench está agora funcionando e e-mails na fila estão sendo reproduzidos. Uma atualização será publicada assim que o replay estiver concluído.

5. 30 Eost 2026 da 19:53 UTCresolved

   Esta questão está resolvida. Entrega de e-mail do Workbench foi restaurado, e phishing envios de e-mail estão processando normalmente. Os e-mails de phishing suspeitos enviados durante este tempo não foram recebidos pela Expel e não puderam ser processados. Por favor, peça aos seus usuários para reenviar tudo o que eles relataram durante este período. Os e-mails de notificação gerados durante este tempo foram entregues. Alguns podem chegar mais tarde do que o timestamp que foram originalmente gerados.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 02:21 UTCinvestigating

   Às 21h58 EDT, começamos a ter um problema com o banco de dados Workbench que está impedindo os usuários de acessar o Workbench. Vamos fornecer uma atualização até às 23h EDT.

2. 17 Gouere 2026 da 02:34 UTCmonitoring

   Implementámos uma solução e acreditamos que o incidente será resolvido. Estamos a acompanhar a saúde das infra-estruturas e resolveremos esta questão se não houver questões pendentes. Por favor, avise-nos se você estiver tendo algum problema.

3. 17 Gouere 2026 da 03:01 UTCresolved

   O incidente foi resolvido, e todos os sistemas estão novamente totalmente disponíveis. Nenhum dado do cliente foi perdido; operações de SOC foram impactadas, mas estão de volta ao normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gouere 2026 da 20:20 UTCinvestigating

   Em 18 de junho, uma mudança foi feita no ambiente da Expel que inadvertidamente introduziu lógica que silenciosamente indexou alertas de fornecedores. Essa mudança foi revertida para restaurar o alerta assim que foi identificado em 1o de julho. Nossa equipe identificou vários alertas que ocorreram durante o período de serviço impactado em uma série de ambientes de clientes que estamos repetindo. Se algum incidente surgir, os clientes impactados serão notificados via Workbench. Entretanto, não hesite em contactar a nossa equipa com perguntas.

2. 12 Eost 2026 da 17:47 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 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. 18 Mezheven 2026 da 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. 18 Mezheven 2026 da 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. 18 Mezheven 2026 da 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. 18 Mezheven 2026 da 23:28 UTCresolved

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

1. 17 Mezheven 2026 da 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. 18 Mezheven 2026 da 00:07 UTCinvestigating

   We are continuing to investigate this issue

3. 18 Mezheven 2026 da 00:59 UTCinvestigating

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

4. 18 Mezheven 2026 da 02:12 UTCinvestigating

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

5. 18 Mezheven 2026 da 03: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. 18 Mezheven 2026 da 13:29 UTCresolved

   This incident has been resolved.

1. 17 Mezheven 2026 da 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. 17 Mezheven 2026 da 16:37 UTCmonitoring

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

3. 17 Mezheven 2026 da 16:59 UTCresolved

   This incident has been resolved.

1. 9 Mezheven 2026 da 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. 9 Mezheven 2026 da 16:42 UTCinvestigating

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

3. 9 Mezheven 2026 da 17:22 UTCmonitoring

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

4. 9 Mezheven 2026 da 17:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 Mezheven 2026 da 17:33 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 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. 13 Mae 2026 da 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. 13 Mae 2026 da 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. 1 Mae 2026 da 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. 1 Mae 2026 da 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. 1 Mae 2026 da 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. 25 Ebrel 2026 da 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. 25 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 20 Ebrel 2026 da 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. 24 Meurzh 2026 da 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. 24 Meurzh 2026 da 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. 24 Meurzh 2026 da 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. 24 Meurzh 2026 da 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. 2 Meurzh 2026 da 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. 2 Meurzh 2026 da 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. 2 Meurzh 2026 da 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. 2 Cʼhwevrer 2026 da 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. 2 Cʼhwevrer 2026 da 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. 2 Cʼhwevrer 2026 da 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. 2 Cʼhwevrer 2026 da 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. 2 Cʼhwevrer 2026 da 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. 2 Cʼhwevrer 2026 da 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. 20 Genver 2026 da 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. 20 Genver 2026 da 20:54 UTCmonitoring

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

3. 20 Genver 2026 da 23:02 UTCresolved

   This incident has been resolved.

1. 7 Genver 2026 da 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. 7 Genver 2026 da 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. 7 Genver 2026 da 22:00 UTCmonitoring

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

4. 7 Genver 2026 da 22:54 UTCresolved

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

1. 29 Kerzu 2025 da 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. 29 Kerzu 2025 da 21:49 UTCmonitoring

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

3. 29 Kerzu 2025 da 22:09 UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. 18 Du 2025 da 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. 18 Du 2025 da 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. 19 Du 2025 da 18:17 UTCresolved

   This incident has been resolved.

1. 12 Du 2025 da 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. 17 Ebrel 2026 da 13:52 UTCresolved

   This incident has been resolved.

1. 3 Du 2025 da 16:56 UTCinvestigating

   At 10:50am ET, we began experiencing a problem with pivoting to Wiz console that resulting in some degraded analyst triage experience. We will provide an update by 12:50pm ET.

2. 3 Du 2025 da 17:50 UTCinvestigating

   We have reached out to Wiz and waiting to hear back. We will provide an update by 1:50pm ET.

3. 3 Du 2025 da 18:55 UTCmonitoring

   Analysts are starting to successfully SSO into the Wiz console. We will continue to monitor the situation. We will provide an update by 3:00pm ET.

4. 3 Du 2025 da 19:43 UTCresolved

   Analysts are able to successfully SSO into the Wiz console. Incident is closed.