Vendor Status Watch

← all vendors

Expel status history

Current state: operational — “All Systems Operational” per https://status.expel.io (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

2incidents, last 30 days
4incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do Expel incidents last?

2.5 hmedian incident duration28 measured
14.3 h90th percentile1 in 10 ran longer
4.4 hmedian, major/critical only14 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-22 15:26 UTCAlert Ingestion Delayedresolvedmajor5 h 37 min
2026-08-30 09:43 UTCEmails from Workbench delayed since 12am UTCresolvedcritical10 h 10 min
2026-07-17 02:21 UTCWorkbench Availability due to Database Issueresolvedcritical40 min
2026-07-13 20:20 UTCIssue affecting some vendor alertsresolvednone29 d 21 h
2026-06-18 20:37 UTCDelayed Notificationsresolvedminor2 h 51 min
2026-06-17 23:11 UTCDelays in processing phishing submissionsresolvedminor14 h 17 min
2026-06-17 16:16 UTCAlert Ingestion Delay for AWS Cloudtrailresolvedminor42 min
2026-06-09 15:40 UTCWorkbench Availabilityresolvednone1 h 53 min
2026-05-13 16:23 UTCWorkbench Expel Alert Count Discrepancyresolvednone22 min
2026-05-01 18:50 UTCSecurity Device Credentials Availabilityresolvedmajor1 h 10 min
2026-04-25 17:42 UTCDelayed Notificationsresolvedminor27 min
2026-04-20 16:20 UTCAlert ingestion delayed for a subset of security devicesresolvedmajor4 h 33 min
2026-03-24 16:58 UTCWorkbench Unable To Deliver Microsoft Teams Notificationsresolvedcritical4 h 14 min
2026-03-02 18:35 UTCAlert Ingestion Outage for AWS GuardDutyresolvedminor2 h 00 min
2026-02-02 21:00 UTCWorkbench Outbound Notifications Delayresolvedcritical1 h 32 min
2026-01-20 20:31 UTCAlert Ingestion Delayresolvedcritical2 h 30 min
2026-01-07 19:51 UTCPhishing Service Sending Multiple Notificationsresolvedminor3 h 02 min
2025-12-29 21:26 UTCDetection pipeline availabilityresolvedmajor42 min
2025-11-18 15:34 UTCDelivery failure for Teams messagesresolvedcritical26 h 43 min
2025-11-12 15:28 UTCService Update: Orca Security Integrationresolvedcritical155 d 22 h
2025-11-03 16:56 UTCWiz Console Login Issuesresolvedminor2 h 47 min
2025-10-29 17:17 UTCAlert Ingest Delay for O365resolvedmajor9 h 05 min
2025-10-20 19:41 UTCWorkbench Availabilityresolvedmajor9 h 18 min
2025-10-20 10:06 UTCAmazon Web Services outage affecting Expel Workbenchresolvednone2 h 28 min
2025-10-17 05:55 UTCFailures sending messages to Microsoft Teams channelsresolvedcritical1 h 03 min
2025-10-09 13:56 UTCThe Alert Analysis Dashboard is not displaying dataresolvedminor28 min
2025-10-08 08:59 UTCDelay in sending email, slack and MS Teams notifications from Workbenchresolvedminor1 h 50 min
2025-09-09 13:17 UTCConsole Login Issues - Impacting certain SSO and Wiz Accountsresolvednone16 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
}