Expel Status

Resolved: The third-party vendor responsible for the issues has provided a workaround which we have implemented in our infrastructure. The incident has been resolved, and all systems are once again fully available.

Monitoring: The third-party vendor responsible for the issues affecting Expel Workbench has taken corrective action, which is improving Workbench availability and data ingestion speeds. No data has been lost. We’re monitoring for further issues, and will provide additional updates as necessary.

Identified: We're making progress addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We will provide our next update by 11:30pm UTC.

Identified: Our team continues to work on addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We will provide our next update by 11:00pm UTC.

Identified: Our team is addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We’re validating a solution and will provide our next update by 10:30pm UTC.

Identified: We're still managing the ongoing issue with a third-party vendor, which continues to affect Expel Workbench availability and slow data ingestion. No data has been lost. Our team is still working on a solution, and we will provide our next update by 10:00pm UTC.

Identified: The ongoing issue with a third-party vendor is still affecting Expel Workbench availability and slowing data ingestion. No data has been lost. We continue to work on a solution and will post our next update by 9:30pm UTC.

Identified: An issue with a third-party vendor is impacting Expel Workbench availability, slowing down data ingestion. No data has been lost. We’re actively working through a solution and will provide an update by 9:00pm UTC.

Identified: We’ve identified an issue with a third-party vendor affecting Expel Workbench availability, and also slowing down our ingestion of data. No data has been lost. We’re monitoring the situation closely and will provide an update by 8:30pm UTC.

Investigating: We are investigating a problem causing Expel Workbench to be intermittently unavailable. We will provide an update by 8:00 PM UTC.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Identified: On May 19th, we temporarily disabled the alert status syncing feature between Expel Workbench and Wiz due to an identified error.

Importantly, this does not affect Expel’s ability to deliver MDR services for Wiz. Workbench continues to ingest alerts from Wiz as expected, and our SOC is actively monitoring and responding.

We will share an update as soon as the fix is deployed and syncing is re-enabled.

Thank you for your understanding.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.

Resolved: The third-party vendor responsible for the issues has provided a workaround which we have implemented in our infrastructure. The incident has been resolved, and all systems are once again fully available.

Monitoring: The third-party vendor responsible for the issues affecting Expel Workbench has taken corrective action, which is improving Workbench availability and data ingestion speeds. No data has been lost. We’re monitoring for further issues, and will provide additional updates as necessary.

Identified: We're making progress addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We will provide our next update by 11:30pm UTC.

Identified: Our team continues to work on addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We will provide our next update by 11:00pm UTC.

Identified: Our team is addressing the issue caused by a third-party vendor, which is still affecting Expel Workbench availability and causing slow data ingestion. No data has been lost. We’re validating a solution and will provide our next update by 10:30pm UTC.

Identified: We're still managing the ongoing issue with a third-party vendor, which continues to affect Expel Workbench availability and slow data ingestion. No data has been lost. Our team is still working on a solution, and we will provide our next update by 10:00pm UTC.

Identified: The ongoing issue with a third-party vendor is still affecting Expel Workbench availability and slowing data ingestion. No data has been lost. We continue to work on a solution and will post our next update by 9:30pm UTC.

Identified: An issue with a third-party vendor is impacting Expel Workbench availability, slowing down data ingestion. No data has been lost. We’re actively working through a solution and will provide an update by 9:00pm UTC.

Identified: We’ve identified an issue with a third-party vendor affecting Expel Workbench availability, and also slowing down our ingestion of data. No data has been lost. We’re monitoring the situation closely and will provide an update by 8:30pm UTC.

Investigating: We are investigating a problem causing Expel Workbench to be intermittently unavailable. We will provide an update by 8:00 PM UTC.

Resolved: The incident has been resolved, and all systems are once again fully available. No customer data was lost.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.

Monitoring: We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.

Monitoring: We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.

Monitoring: Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery.

This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.