Cronologia delle interruzioni di Expel

1. 22 settembre 2026 alle ore 15:26 UTCinvestigating

   Alle 10:30 abbiamo iniziato a sperimentare un problema con l'ingestione all'erta. Le operazioni SOC sono colpite, ma si riprenderà una volta che il servizio viene ripristinato; nessun dato verrà perso. Forniremo un aggiornamento entro le 12:30 PM ET.

2. 22 settembre 2026 alle ore 16:21 UTCinvestigating

   Alle 10:30 abbiamo iniziato a sperimentare un problema con l'ingestione all'erta. Le operazioni SOC sono colpite, ma si riprenderà una volta che il servizio viene ripristinato; nessun dato verrà perso. Forniamo un aggiornamento di 1:30PM ET.

3. 22 settembre 2026 alle ore 17:28 UTCinvestigating

   Alle 10:30 abbiamo iniziato a sperimentare un problema con l'ingestione all'erta. Le operazioni SOC sono colpite, ma si riprenderà una volta che il servizio viene ripristinato; nessun dato verrà perso. Forneremo un aggiornamento di 2:30PM ET.

4. 22 settembre 2026 alle ore 18:24 UTCinvestigating

   Alle 10:30 abbiamo iniziato a sperimentare un problema con l'ingestione all'erta. Le operazioni SOC sono colpite, ma si riprenderà una volta che il servizio viene ripristinato; nessun dato verrà perso. Forniamo un aggiornamento di 3:30PM ET.

5. 22 settembre 2026 alle ore 19:13 UTCmonitoring

   Abbiamo implementato una soluzione e crediamo che l'incidente sia risolto. Stiamo monitorando la salute dell'infrastruttura e risolveremo questo problema se non ci sono problemi eccezionali. Vi preghiamo di farci sapere se avete problemi.

6. 22 settembre 2026 alle ore 21:03 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 30 agosto 2026 alle ore 09:43 UTCidentified

   Le e-mail da Workbench sono ritardate da 12am UTC. Abbiamo identificato la causa principale e stiamo lavorando a una bonifica. Le risposte dei risultati di phishing, le notifiche di posta elettronica dell'utente e le notifiche di ticketing di Org-Level Email sono ritardate dal 12am UTC. Le operazioni SOC e l'ingestione degli avvisi non sono influenzate. Forneremo un altro aggiornamento di 12:30pm UTC

2. 30 agosto 2026 alle ore 11:10 UTCidentified

   Abbiamo identificato la causa che continua a lavorare sulla bonifica. Abbiamo anche confermato che a causa di questo problema, quando qualcuno invia una sospetta e-mail di phishing, l'email non raggiunge Workbench per la revisione. Prossimo aggiornamento alle 1pm UTC.

3. 30 agosto 2026 alle ore 12:58 UTCidentified

   Stiamo continuando a lavorare sulla bonifica. I servizi MDR non sono influenzati. L'ingestione, il rilevamento e l'indagine all'erta funzionano normalmente. Le notifiche Slack, Microsoft Teams, PagerDuty, Opsgenie e Service Now sono ancora in fase di consegna. La consegna via email da Workbench non è disponibile. Non è richiesta alcuna azione in questo momento; confermeremo i passaggi di resubmission per le presentazioni di phishing una volta che il servizio è ripristinato. Prossimo aggiornamento: lunedì 31 agosto alle 13:00 UTC (9:00 AM ET)

4. 30 agosto 2026 alle ore 18:14 UTCmonitoring

   La consegna via e-mail da Workbench ora funziona e le e-mail in coda vengono riprodotte. Un aggiornamento verrà pubblicato una volta completata la riproduzione.

5. 30 agosto 2026 alle ore 19:53 UTCresolved

   Questo problema è risolto. La consegna via e-mail da Workbench è stata ripristinata e le email di phishing vengono elaborate normalmente. Le e-mail di phishing sospette presentate durante questo periodo non sono state ricevute da Expel e non potrebbero essere elaborate. Si prega di chiedere agli utenti di resubmit tutto ciò che hanno segnalato durante questo periodo. Le email di notifica generate durante questo periodo sono state consegnate. Alcuni possono arrivare più tardi del timestamp che sono stati originariamente generati.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 17 luglio 2026 alle ore 02:21 UTCinvestigating

   A 9:58 pm EDT, abbiamo iniziato a sperimentare un problema con il database Workbench che sta impedendo agli utenti di accedere Workbench. Forniamo un aggiornamento di 11pm EDT.

2. 17 luglio 2026 alle ore 02:34 UTCmonitoring

   Abbiamo implementato una soluzione e crediamo che l'incidente sia risolto. Stiamo monitorando la salute dell'infrastruttura e risolveremo questo problema se non ci sono problemi eccezionali. Vi preghiamo di farci sapere se avete problemi.

3. 17 luglio 2026 alle ore 03:01 UTCresolved

   L'incidente è stato risolto, e tutti i sistemi sono ancora una volta completamente disponibili. Nessun dato del cliente è stato perso; le operazioni SOC sono state influenzate, ma sono tornati alla normalità.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 luglio 2026 alle ore 20:20 UTCinvestigating

   Il 18 giugno è stato fatto un cambiamento nell'ambiente di Expel che inavvertitamente introdusse la logica che silenziosamente indicizzò gli avvisi dei venditori. Questa modifica è stata annullata per ripristinare l'avviso non appena è stato identificato il 1 luglio. Il nostro team ha identificato diversi avvisi che si sono verificati durante il periodo di servizio impatto entro un certo numero di ambienti clienti che stiamo rielaborando. Se si verificano incidenti, i clienti colpiti verranno notificati tramite Workbench. Nel frattempo non esitate a raggiungere il nostro team con qualsiasi domanda.

2. 12 agosto 2026 alle ore 17:47 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 23:28 UTCresolved

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

1. 17 giugno 2026 alle ore 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 giugno 2026 alle ore 00:07 UTCinvestigating

   We are continuing to investigate this issue

3. 18 giugno 2026 alle ore 00:59 UTCinvestigating

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

4. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 13:29 UTCresolved

   This incident has been resolved.

1. 17 giugno 2026 alle ore 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 giugno 2026 alle ore 16:37 UTCmonitoring

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

3. 17 giugno 2026 alle ore 16:59 UTCresolved

   This incident has been resolved.

1. 9 giugno 2026 alle ore 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 giugno 2026 alle ore 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 giugno 2026 alle ore 17:22 UTCmonitoring

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

4. 9 giugno 2026 alle ore 17:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 giugno 2026 alle ore 17:33 UTCresolved

   This incident has been resolved.

1. 13 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 20:54 UTCmonitoring

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

3. 20 gennaio 2026 alle ore 23:02 UTCresolved

   This incident has been resolved.

1. 7 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 22:00 UTCmonitoring

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

4. 7 gennaio 2026 alle ore 22:54 UTCresolved

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

1. 29 dicembre 2025 alle ore 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 dicembre 2025 alle ore 21:49 UTCmonitoring

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

3. 29 dicembre 2025 alle ore 22:09 UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. 18 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 18:17 UTCresolved

   This incident has been resolved.

1. 12 novembre 2025 alle ore 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 aprile 2026 alle ore 13:52 UTCresolved

   This incident has been resolved.