Expel status history
Current state: operational — “All Systems Operational” per https://status.expel.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Expel incidents last?
From 28 incidents with a vendor-posted start and resolve time. Longest on record: Service Update: Orca Security Integration — 155.9 days (2025-11-12 15:28 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (28)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-30 09:43 UTC | Emails from Workbench delayed since 12am UTC | resolved | critical | 10 h 10 min |
| 2026-07-17 02:21 UTC | Workbench Availability due to Database Issue | resolved | critical | 40 min |
| 2026-07-13 20:20 UTC | Issue affecting some vendor alerts | resolved | none | 29 d 21 h |
| 2026-06-18 20:37 UTC | Delayed Notifications | resolved | minor | 2 h 51 min |
| 2026-06-17 23:11 UTC | Delays in processing phishing submissions | resolved | minor | 14 h 17 min |
| 2026-06-17 16:16 UTC | Alert Ingestion Delay for AWS Cloudtrail | resolved | minor | 42 min |
| 2026-06-09 15:40 UTC | Workbench Availability | resolved | none | 1 h 53 min |
| 2026-05-13 16:23 UTC | Workbench Expel Alert Count Discrepancy | resolved | none | 22 min |
| 2026-05-01 18:50 UTC | Security Device Credentials Availability | resolved | major | 1 h 10 min |
| 2026-04-25 17:42 UTC | Delayed Notifications | resolved | minor | 27 min |
| 2026-04-20 16:20 UTC | Alert ingestion delayed for a subset of security devices | resolved | major | 4 h 33 min |
| 2026-03-24 16:58 UTC | Workbench Unable To Deliver Microsoft Teams Notifications | resolved | critical | 4 h 14 min |
| 2026-03-02 18:35 UTC | Alert Ingestion Outage for AWS GuardDuty | resolved | minor | 2 h 00 min |
| 2026-02-02 21:00 UTC | Workbench Outbound Notifications Delay | resolved | critical | 1 h 32 min |
| 2026-01-20 20:31 UTC | Alert Ingestion Delay | resolved | critical | 2 h 30 min |
| 2026-01-07 19:51 UTC | Phishing Service Sending Multiple Notifications | resolved | minor | 3 h 02 min |
| 2025-12-29 21:26 UTC | Detection pipeline availability | resolved | major | 42 min |
| 2025-11-18 15:34 UTC | Delivery failure for Teams messages | resolved | critical | 26 h 43 min |
| 2025-11-12 15:28 UTC | Service Update: Orca Security Integration | resolved | critical | 155 d 22 h |
| 2025-11-03 16:56 UTC | Wiz Console Login Issues | resolved | minor | 2 h 47 min |
| 2025-10-29 17:17 UTC | Alert Ingest Delay for O365 | resolved | major | 9 h 05 min |
| 2025-10-20 19:41 UTC | Workbench Availability | resolved | major | 9 h 18 min |
| 2025-10-20 10:06 UTC | Amazon Web Services outage affecting Expel Workbench | resolved | none | 2 h 28 min |
| 2025-10-17 05:55 UTC | Failures sending messages to Microsoft Teams channels | resolved | critical | 1 h 03 min |
| 2025-10-09 13:56 UTC | The Alert Analysis Dashboard is not displaying data | resolved | minor | 28 min |
| 2025-10-08 08:59 UTC | Delay in sending email, slack and MS Teams notifications from Workbench | resolved | minor | 1 h 50 min |
| 2025-09-09 13:17 UTC | Console Login Issues - Impacting certain SSO and Wiz Accounts | resolved | none | 16 min |
| 2025-08-20 01:24 UTC | Alert Ingestion for Azure | resolved | major | 4 h 46 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Expel with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"expel"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}