Historial de interrupciones de Expel

1. August 30, 2026 at 9:43 AM UTCidentified

   Los correos electrónicos del Workbench se retrasan desde 12am UTC. Hemos identificado la causa raíz y estamos trabajando en una rehabilitación. Las respuestas de los resultados de Phishing, notificaciones de correo electrónico de usuario y notificaciones de tickets de correo electrónico de Org-Level se retrasan desde las 12am UTC. Las operaciones de SOC y la ingestión alerta no se ven afectadas. Proporcionaremos otra actualización a las 12:30pm UTC

2. August 30, 2026 at 11:10 AM UTCidentified

   Hemos identificado la causa sigue trabajando en la rehabilitación. También hemos confirmado que debido a este problema, cuando alguien envía un correo electrónico de phishing sospechoso, el correo electrónico no llegará a Workbench para su revisión. Siguiente actualización a las 1pm UTC.

3. August 30, 2026 at 12:58 PM UTCidentified

   Continuamos trabajando en la rehabilitación. Los servicios de MDR no son afectados. La ingestión de alerta, la detección y la investigación funcionan normalmente. Slack, Microsoft Teams, PagerDuty, Opsgenie y Service Now notificaciones todavía están siendo entregadas. El envío de correo electrónico desde Workbench sigue sin estar disponible. No se requiere ninguna acción en este momento; confirmaremos los pasos de reingreso para las presentaciones de phishing una vez restaurado el servicio. Siguiente actualización: lunes 31 de agosto a las 13:00 UTC (9:00 AM ET)

4. August 30, 2026 at 6:14 PM UTCmonitoring

   La entrega de correo electrónico de Workbench está trabajando y los correos electrónicos en la cola están siendo reproducidos. Una actualización será publicada una vez que la repetición esté completa.

5. August 30, 2026 at 7:53 PM UTCresolved

   Esta cuestión se resuelve. La entrega de correo electrónico de Workbench ha sido restaurada, y los envíos de correo electrónico de phishing se procesan normalmente. Los correos electrónicos falsos sospechosos enviados durante este tiempo no fueron recibidos por Expel y no pudieron ser procesados. Por favor, pida a sus usuarios que vuelvan a presentar cualquier información que reporten durante este período. Se han entregado correos electrónicos de notificación generados durante este tiempo. Algunos pueden llegar más tarde que el timetamp que originalmente fueron generados.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 2:21 AM UTCinvestigating

   A las 9:58pm EDT, comenzamos a experimentar un problema con la base de datos Workbench que impide a los usuarios acceder a Workbench. Proporcionaremos una actualización para las 11pm EDT.

2. July 17, 2026 at 2:34 AM UTCmonitoring

   Hemos implementado una solución y creemos que el incidente se resolverá. Estamos monitoreando la salud de la infraestructura y resolveremos esto si no hay problemas pendientes. Por favor háganos saber si está experimentando algún problema.

3. July 17, 2026 at 3:01 AM UTCresolved

   El incidente se ha resuelto y todos los sistemas están de nuevo totalmente disponibles. No se perdieron datos de clientes; las operaciones de SOC fueron impactadas, pero vuelven a la normalidad.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 8:20 PM UTCinvestigating

   El 18 de junio, se realizó un cambio en el entorno de Expel que introdujo inadvertidamente la lógica que indignó silenciosamente las alertas del vendedor. Este cambio fue revertido para restaurar la alerta tan pronto como se identificó el 1 de julio. Nuestro equipo ha identificado varias alertas que ocurrieron durante el período de servicio impactado dentro de varios entornos de clientes que estamos reproduciendo. Si surgen incidentes, los clientes afectados serán notificados a través de Workbench. Mientras tanto, por favor no dude en contactar con nuestro equipo con cualquier pregunta.

2. August 12, 2026 at 5:47 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 18, 2026 at 8:37 PM 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. June 18, 2026 at 9:05 PM 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. June 18, 2026 at 9:35 PM 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. June 18, 2026 at 10:13 PM 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. June 18, 2026 at 11:28 PM UTCresolved

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

1. June 17, 2026 at 11:11 PM 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. June 18, 2026 at 12:07 AM UTCinvestigating

   We are continuing to investigate this issue

3. June 18, 2026 at 12:59 AM UTCinvestigating

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

4. June 18, 2026 at 2:12 AM UTCinvestigating

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

5. June 18, 2026 at 3:17 AM 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. June 18, 2026 at 1:29 PM UTCresolved

   This incident has been resolved.

1. June 17, 2026 at 4:16 PM 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. June 17, 2026 at 4:37 PM UTCmonitoring

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

3. June 17, 2026 at 4:59 PM UTCresolved

   This incident has been resolved.

1. June 9, 2026 at 3:40 PM 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. June 9, 2026 at 4:42 PM UTCinvestigating

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

3. June 9, 2026 at 5:22 PM UTCmonitoring

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

4. June 9, 2026 at 5:24 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. June 9, 2026 at 5:33 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 4:23 PM 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. May 13, 2026 at 4:38 PM 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. May 13, 2026 at 4:46 PM 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. May 1, 2026 at 6:50 PM 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. May 1, 2026 at 7:09 PM 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. May 1, 2026 at 8:01 PM 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. April 25, 2026 at 5:42 PM 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. April 25, 2026 at 6:09 PM UTCresolved

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

1. April 20, 2026 at 4:20 PM 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. April 20, 2026 at 5:00 PM 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. April 20, 2026 at 5:35 PM 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. April 20, 2026 at 6:01 PM 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. April 20, 2026 at 6:34 PM 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. April 20, 2026 at 7:02 PM 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. April 20, 2026 at 7:34 PM 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. April 20, 2026 at 8:01 PM 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. April 20, 2026 at 8:54 PM 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. March 24, 2026 at 4:58 PM 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. March 24, 2026 at 5:49 PM 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. March 24, 2026 at 9:02 PM 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. March 24, 2026 at 9:12 PM 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. March 2, 2026 at 6:35 PM 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. March 2, 2026 at 7:36 PM 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. March 2, 2026 at 8:36 PM 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. February 2, 2026 at 9:00 PM 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. February 2, 2026 at 9:15 PM 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. February 2, 2026 at 9:41 PM 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. February 2, 2026 at 10:00 PM 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. February 2, 2026 at 10:12 PM 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. February 2, 2026 at 10:33 PM 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. January 20, 2026 at 8:31 PM UTCinvestigating

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

2. January 20, 2026 at 8:54 PM UTCmonitoring

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

3. January 20, 2026 at 11:02 PM UTCresolved

   This incident has been resolved.

1. January 7, 2026 at 7:51 PM 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. January 7, 2026 at 9:11 PM 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. January 7, 2026 at 10:00 PM UTCmonitoring

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

4. January 7, 2026 at 10:54 PM UTCresolved

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

1. December 29, 2025 at 9:26 PM 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. December 29, 2025 at 9:49 PM UTCmonitoring

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

3. December 29, 2025 at 10:09 PM UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. November 18, 2025 at 3:34 PM 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. November 18, 2025 at 3:50 PM 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. November 19, 2025 at 6:17 PM UTCresolved

   This incident has been resolved.

1. November 12, 2025 at 3:28 PM 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. April 17, 2026 at 1:52 PM UTCresolved

   This incident has been resolved.

1. November 3, 2025 at 4:56 PM 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. November 3, 2025 at 5:50 PM UTCinvestigating

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

3. November 3, 2025 at 6:55 PM 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. November 3, 2025 at 7:43 PM UTCresolved

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