Expel driftsforstyrrelser

1. 30. august 2026 kl. 09.43 UTCidentified

   E-mails fra Workbench er forsinket siden 12 am UTC. Vi har identificeret årsagen og arbejder på en oprydning. Phishing resultat svar, bruger e-mail meddelelser, og Org- Level e-mail ticket meddelelser er forsinket siden 12 am UTC. SOC-operationer og alarmindtagelse påvirkes ikke. Vi vil levere endnu en opdatering kl 12: 30 UTC

2. 30. august 2026 kl. 11.10 UTCidentified

   Vi har identificeret årsagen fortsætter med at arbejde med oprensning. Vi har også bekræftet, at på grund af dette problem, når nogen indgiver en mistanke phishing e-mail, vil e-mailen ikke nå Workbench for gennemgang. Næste opdatering kl. 13 UTC.

3. 30. august 2026 kl. 12.58 UTCidentified

   Vi fortsætter med at arbejde med oprydning. MDR-tjenester påvirkes ikke. Alert indtagelse, afsløring og efterforskning fungerer normalt. Slack, Microsoft Teams, PagerDuty, Opsgenie, og Service Now meddelelser er stadig ved at blive leveret. Email levering fra Workbench forbliver utilgængelig. Der kræves ingen handling på dette tidspunkt; vi vil bekræfte genopførelsestrin for phishing indlæg, når tjenesten er genoprettet. Næste opdatering: Mandag, 31 August på 13: 00 UTC (9: 00 AM ET)

4. 30. august 2026 kl. 18.14 UTCmonitoring

   Email levering fra Workbench er nu arbejder og e-mails i køen bliver genspillet. En opdatering vil blive bogført, når genafspilningen er færdig.

5. 30. august 2026 kl. 19.53 UTCresolved

   Dette spørgsmål er løst. E-mail levering fra Workbench er blevet genoprettet, og phishing e-mail indlæg er behandling normalt. Mistænkte phishing e-mails indsendt i løbet af denne periode blev ikke modtaget af Expel og kunne ikke behandles. Bed dine brugere om at genindsende alt, de rapporterede i denne periode. Anmeldelse e-mails genereret i løbet af denne tid er blevet leveret. Nogle kan ankomme senere end det tidsstempel, de oprindeligt blev genereret.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 02.21 UTCinvestigating

   Kl 9: 58pm EDT, vi begyndte at opleve et problem med Workbench database, der forhindrer brugerne i at få adgang til Workbench. Vi vil levere en opdatering inden kl. 23.

2. 17. juli 2026 kl. 02.34 UTCmonitoring

   Vi har gennemført en rettelse og mener, at hændelsen skal løses. Vi overvåger infrastrukturens sundhed og vil løse dette, hvis der ikke er udestående spørgsmål. Sig til, hvis du har problemer.

3. 17. juli 2026 kl. 03.01 UTCresolved

   Hændelsen er blevet løst, og alle systemer er igen fuldt tilgængelige. Ingen kunde data blev tabt; SOC operationer blev påvirket, men er tilbage til normal.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. juli 2026 kl. 20.20 UTCinvestigating

   Den 18. juni blev der foretaget en ændring i Expel miljø, der utilsigtet indført logik, der lydløst indekseret sælger advarsler. Denne ændring blev vendt tilbage for at genoprette alarmering, så snart det blev identificeret den 1. juli. Vores team har identificeret flere advarsler, der opstod i løbet af den ramte service periode inden for en række kundemiljøer, som vi genspiller. Hvis nogen hændelser overflade, ramte kunder vil blive underrettet via Workbench. I mellemtiden skal du ikke tøve med at kontakte vores team med spørgsmål.

2. 12. august 2026 kl. 17.47 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 23.28 UTCresolved

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

1. 17. juni 2026 kl. 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. juni 2026 kl. 00.07 UTCinvestigating

   We are continuing to investigate this issue

3. 18. juni 2026 kl. 00.59 UTCinvestigating

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

4. 18. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 13.29 UTCresolved

   This incident has been resolved.

1. 17. juni 2026 kl. 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. juni 2026 kl. 16.37 UTCmonitoring

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

3. 17. juni 2026 kl. 16.59 UTCresolved

   This incident has been resolved.

1. 9. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 17.22 UTCmonitoring

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

4. 9. juni 2026 kl. 17.24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9. juni 2026 kl. 17.33 UTCresolved

   This incident has been resolved.

1. 13. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 20.54 UTCmonitoring

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

3. 20. januar 2026 kl. 23.02 UTCresolved

   This incident has been resolved.

1. 7. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 22.00 UTCmonitoring

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

4. 7. januar 2026 kl. 22.54 UTCresolved

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

1. 29. december 2025 kl. 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. december 2025 kl. 21.49 UTCmonitoring

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

3. 29. december 2025 kl. 22.09 UTCresolved

   Detection pipelines are caught up. Service is nominal.

1. 18. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 18.17 UTCresolved

   This incident has been resolved.

1. 12. november 2025 kl. 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. april 2026 kl. 13.52 UTCresolved

   This incident has been resolved.

1. 3. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 19.43 UTCresolved

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