Expel Outage History

Expel is up right now

Expel had 27 outages in the last 2 years totaling 5495h 26m of downtime — averaging 1.1 incidents per month.

There were 27 Expel outages since June 6, 2025 totaling 5495h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.expel.io

Minor June 11, 2025

Service Update: Wiz Alert Status Syncing

Detected by Pingoru
Jun 11, 2025, 05:13 PM UTC
Resolved
Jan 26, 2026, 03:22 PM UTC
Duration
228d 22h
Affected: Ticketing systems (via email, such as Jira)
Timeline · 2 updates
  1. identified Jun 11, 2025, 05:13 PM UTC

    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.

  2. resolved Jan 26, 2026, 03:22 PM UTC

    Resolved - On January 23rd we have fixed and re-enabled alert status syncing between Expel Workbench and Wiz. If alert status syncing is not working as expected, please ensure the required permissions outlined in the Setup Guide are provided.

Read the full incident report →

Major June 6, 2025

Investigations inadvertent metadata update

Detected by Pingoru
Jun 06, 2025, 01:22 AM UTC
Resolved
Jun 06, 2025, 02:39 AM UTC
Duration
1h 17m
Timeline · 3 updates
  1. identified Jun 06, 2025, 01:22 AM UTC

    At approximately 11:20 am Eastern Time "updated at" metadata for Investigation records were incorrectly altered to a more recent time. This has triggered unintentional notifications to organizations. We are currently working to restore the correct "updated at" metadata for these records

  2. monitoring Jun 06, 2025, 02:12 AM UTC

    We have corrected the incorrect "updated at" metadata for investigation records and we are currently monitoring system activity.

  3. resolved Jun 06, 2025, 02:39 AM UTC

    We have restored the correct "updated at" metadata for these records. No further unintentional notifications should be triggered.

Read the full incident report →