Istoricul incidentelor Expel

1. 30 august 2026 la 09:43 UTCidentified

   E-mailurile de la Workbench sunt amânate de la 12 am UTC. Am identificat cauza principală şi lucrăm la o remediere. Raspunsul final Phishing, notificări de e-mail de utilizator, și notificări de e-mail la nivelul Org sunt întârziate de la 12 AM UTC. Operaţiunile SOC şi ingestiea de alertă nu sunt afectate. Vom furniza o altă actualizare până la 12:30 pm UTC

2. 30 august 2026 la 11:10 UTCidentified

   Am identificat cauza continuă să lucreze la remediere. Am confirmat, de asemenea, că, din cauza acestei probleme, atunci când cineva prezintă un e-mail de phishing suspectate, email-ul nu va ajunge la Workbench pentru revizuire. Următoarea actualizare la 01 UTC.

3. 30 august 2026 la 12:58 UTCidentified

   Continuăm să lucrăm la remediere. Serviciile MDR nu sunt afectate. Alerta ingerare, detectare, și de investigare funcționează în mod normal. Slack, Microsoft Teams, PagerDuty, Opsgenie şi Service Now sunt încă în curs de livrare. Livrarea prin email de la Workbench rămâne indisponibilă. Nu este necesară nicio acțiune în acest moment; vom confirma pașii de readmitere pentru phishing transmiteri odată ce serviciul este restabilit. Următoarea actualizare: luni, 31 august, ora 13:00 UTC (9:00 ET)

4. 30 august 2026 la 18:14 UTCmonitoring

   Livrarea de e-mail de la Workbench este acum de lucru și e-mail-uri în coada sunt reluarea. O actualizare va fi postată odată ce reluarea este completă.

5. 30 august 2026 la 19:53 UTCresolved

   Această problemă este rezolvată. Livrarea prin e-mail de la Workbench a fost restaurată, iar phishing e-mail-urile sunt de procesare în mod normal. E-mailuri de phishing suspectate depuse în acest timp nu au fost primite de Expel și nu au putut fi prelucrate. Vă rugăm să cereţi utilizatorilor să refacă tot ce au raportat în această perioadă. E-mailuri de notificare generate în acest timp au fost livrate. Unii ar putea ajunge mai târziu decât marca de timp au fost inițial generate.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iulie 2026 la 02:21 UTCinvestigating

   La 9:58pm EDT, am început să avem o problemă cu baza de date Workbench care împiedică utilizatorii să acceseze Workbench. Vom oferi o actualizare de 11 pm EDT.

2. 17 iulie 2026 la 02:34 UTCmonitoring

   Am implementat o soluţie şi credem că incidentul va fi rezolvat. Monitorizăm sănătatea infrastructurii și vom rezolva acest lucru dacă nu există probleme nerezolvate. Vă rugăm să ne anunţaţi dacă aveţi probleme.

3. 17 iulie 2026 la 03:01 UTCresolved

   Incidentul a fost rezolvat şi toate sistemele sunt încă o dată complet disponibile. Nu s-au pierdut date despre clienți; operațiunile SOC au fost afectate, dar au revenit la normal.

Traducere automată din actualizarea oficială a incidentului.

1. 13 iulie 2026 la 20:20 UTCinvestigating

   Pe 18 iunie s-a făcut o schimbare în mediul lui Expel care a introdus din greşeală logica care a indexat în tăcere alertele vânzătorilor. Această modificare a fost reversibilă pentru a restabili alertarea imediat ce a fost identificată pe 1 iulie. Echipa noastră a identificat mai multe alerte care au avut loc în timpul perioadei de servicii afectate într-un număr de medii de clienți pe care le reluăm. Dacă apar incidente, clienții afectați vor fi notificați prin intermediul Workbench. Între timp, vă rugăm să nu ezitați să ajungă la echipa noastră cu orice întrebări.

2. 12 august 2026 la 17:47 UTCresolved

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

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

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

1. 17 iunie 2026 la 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 iunie 2026 la 00:07 UTCinvestigating

   We are continuing to investigate this issue

3. 18 iunie 2026 la 00:59 UTCinvestigating

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

4. 18 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 13:29 UTCresolved

   This incident has been resolved.

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

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

3. 17 iunie 2026 la 16:59 UTCresolved

   This incident has been resolved.

1. 9 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 17:22 UTCmonitoring

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

4. 9 iunie 2026 la 17:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 iunie 2026 la 17:33 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 20:54 UTCmonitoring

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

3. 20 ianuarie 2026 la 23:02 UTCresolved

   This incident has been resolved.

1. 7 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 22:00 UTCmonitoring

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

4. 7 ianuarie 2026 la 22:54 UTCresolved

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

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

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

3. 29 decembrie 2025 la 22:09 UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. 18 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 18:17 UTCresolved

   This incident has been resolved.

1. 12 noiembrie 2025 la 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 aprilie 2026 la 13:52 UTCresolved

   This incident has been resolved.

1. 3 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 19:43 UTCresolved

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