Expel incident

Workbench Outbound Notifications Delay

Critical Resolved View vendor source →

Expel experienced a critical incident on February 2, 2026 affecting Email and Slack and 1 more component, lasting 1h 32m. The incident has been resolved; the full update timeline is below.

Started
Feb 02, 2026, 09:00 PM UTC
Resolved
Feb 02, 2026, 10:33 PM UTC
Duration
1h 32m
Detected by Pingoru
Feb 02, 2026, 09:00 PM UTC

Affected components

EmailSlackTeamsTicketing systems (via email, such as Jira)PagerDutyOpsgenie

Update timeline

  1. investigating Feb 02, 2026, 09:00 PM UTC

    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. identified Feb 02, 2026, 09:15 PM UTC

    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. identified Feb 02, 2026, 09:41 PM UTC

    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. identified Feb 02, 2026, 10:00 PM UTC

    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. monitoring Feb 02, 2026, 10:12 PM UTC

    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. resolved Feb 02, 2026, 10:33 PM UTC

    The incident has been resolved, and all delayed notifications have been delivered. No customer data was lost, and SOC operations were not impacted.