New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Services Pricing Dashboard

Expel, Inc. Outage History

Uptime record, past incidents, and downtime history for Expel, Inc..

Checking current status...
70.3% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Mar 30Jun 27

Monthly Uptime

Month Uptime Days Tracked Days with Issues
June 2026 88.9% 27 3
May 2026 93.5% 31 2
April 2026 36.7% 30 19
March 2026 0% 3 3

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Mar 29 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

June 2026
Delayed Notifications
minor

Started: Jun 18, 8:37 PM

monitoring
The cause of the notification delays has been resolved and we are observing delayed messages being delivered. All delayed notifications will be processed and we will continue to monitor.
Jun 18, 10:13 PM
identified
Workbench notifications continue to be delayed since 19:09 UTC due to an issue with a third-party notification vendor. They are working on a fix. All delayed notifications will be processed once the outage is resolved. Next update 22:00 UTC
Jun 18, 9:35 PM
identified
We've identified the cause of the delayed notifications as an issue with a third-party notification vendor. A fix is currently being applied. Workbench notifications have been delayed since 19:09 UTC, and we'll provide another update at 21:30 UTC.
Jun 18, 9:05 PM
investigating
At 2pm ET, we began experiencing a problem with our notification system that is causing notification delays to our customers. We will provide an update by 5pm ET.
Jun 18, 8:37 PM
Delays in processing phishing submissions
minor

Started: Jun 17, 11:11 PM

investigating
Beginning at 19:47 UTC, phishing submissions are not being processed, which is preventing the creation of Phishing Expel Alerts. Suspected phishing emails submitted for review during this period may not yet be analyzed. We've identified the cause and we are working with the vendor to address the issue. We expect to retrieve and process them once service is restored.
Jun 18, 3:17 AM
investigating
We think we have identified the problem and are working on a resolution right now. Will update again in 60 minutes.
Jun 18, 2:12 AM
investigating
We are continuing to investigate this issue. Will post another update in 60 minutes.
Jun 18, 12:59 AM
investigating
We are continuing to investigate this issue
Jun 18, 12:07 AM
investigating
We are investigating an issue affecting the processing of phishing submissions. Beginning at 19:47 UTC, phishing submissions are not being processed, which is preventing the creation of Phishing Expel Alerts. Suspected phishing emails submitted for review during this period may not yet be analyzed. Our team is actively working to identify the cause. We will provide an update by 00:00 UTC.
Jun 17, 11:11 PM
Alert Ingestion Delay for AWS Cloudtrail
minor

Started: Jun 17, 4:16 PM

monitoring
A fix has been implemented and we are monitoring the results.
Jun 17, 4:37 PM
investigating
At 10am ET, we began experiencing a problem with alert ingestion for some AWS Cloudtrail devices. We will provide an update by 1pm ET.
Jun 17, 4:16 PM
Workbench Availability

Started: Jun 9, 3:40 PM

monitoring
We are continuing to monitor for any further issues.
Jun 9, 5:24 PM
monitoring
We have identified the issue, have rolled out a fix and are monitoring the situation.
Jun 9, 5:22 PM
investigating
Workbench is still experiencing connectivity issues. We are still investigating the issue and will provide an update in 1 hour.
Jun 9, 4:42 PM
investigating
Workbench is currently experiencing connectivity issues and may be inaccessible for some users. We are investigating the issue and will provide an update within an hour.
Jun 9, 3:40 PM
May 2026
Workbench Expel Alert Count Discrepancy

Started: May 13, 4:23 PM

identified
We have remediated the issue with Expel Alerts count being inflated for customers by shifting to a different source of statistics. We are working on fixing the underlying issue with our main source of count data. We will provide another update by 1pm EDT.
May 13, 4:38 PM
identified
We are aware of an issue with the Expel Alerts count being inflated for customers. We have identified the root cause and are working on a remediation. SOC operations and alert ingestion are not affected. We will provide another update by 1pm EDT.
May 13, 4:23 PM
Security Device Credentials Availability
major

Started: May 1, 6:50 PM

monitoring
We have implemented a fix and believe the incident to be resolved. We are seeing customer security devices returning to healthy status. We are monitoring the health of the infrastructure and will post another update by 4pm EDT.
May 1, 7:09 PM
investigating
At 2pm EDT, we began experiencing a problem with the customer device secrets service that is preventing our infrastructure from accessing customer security devices. We will provide an update by 3:30pm EDT.
May 1, 6:50 PM
April 2026
Delayed Notifications
minor

Started: Apr 25, 5:42 PM

investigating
At 1pm ET, we began experiencing a problem with our notification system that is causing notification delays to our customers.  We will provide an update by 2:30pm ET.
Apr 25, 5:42 PM
Alert ingestion delayed for a subset of security devices
major

Started: Apr 20, 4:20 PM

monitoring
We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We are investigating the remaining unhealthy devices, which do not seem related to credentials. We will provide another update by 4:30pm EDT.
Apr 20, 8:01 PM
monitoring
We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We are investigating the remaining unhealthy devices, which do not seem related to the credentials. We will provide another update by 4:00pm EDT.
Apr 20, 7:34 PM
identified
We have restored the credentials for the subset of devices. We are monitoring closely to ensure proper ingestion of delayed alerts. We will provide another update by 3:30pm EDT.
Apr 20, 7:02 PM
identified
We have restored the credentials for the affected subset of devices. We are monitoring closely to ensure proper ingestion of delayed alerts. We will provide another update by 3:00pm EDT.
Apr 20, 6:34 PM
investigating
We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 2:30pm EDT.
Apr 20, 6:01 PM
investigating
We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 2:00pm EDT.
Apr 20, 5:35 PM
investigating
We have identified the specific subset of devices that are affected and are working on restoring the credentials for those devices. Once restored, all alerts that have not been ingested for these devices will be ingested. We will provide another update by 1:30pm EDT.
Apr 20, 5:00 PM
investigating
At 10:59AM EDT, we noticed that a set of devices have been unhealthy since last week due to invalid credentials. We believe the cause to be a change to our device credentials storage subsystem. We are working to identify the specific set of devices and restore the credentials. Once restored, all delayed alerts will be ingested. We will provide an updated by 1pm EDT.
Apr 20, 4:20 PM
November 2025
Service Update: Orca Security Integration
critical

Started: Nov 12, 3:28 PM

identified
We’re upgrading our API connection and that may impact delivery of some alerts to Workbench. We are actively investigating and collaborating on a solution to ensure the consistent and complete delivery of all alert data. Please reach out to Orca if you’d like additional information. Thank you for your patience and understanding as we work through this.
Nov 12, 3:28 PM