Is Expel down?
Last checked 8m agoNo incidents right now.
Expel is operational right now. Last checked 8m ago; the most recent incident resolved 4d ago.
Real-time Expel status, recent outages, and incident history — pulled directly from Expel's official status page at https://status.expel.io every 5 minutes. Pingoru tracks 15 Expel services and has captured 6 incidents in the last 90 days (99.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Expel reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Workbench global network connectivity
Timeline · 5 updates
- investigating · Jun 09, 2026, 03:40 PM UTC
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.
- investigating · Jun 09, 2026, 04:42 PM UTC
Workbench is still experiencing connectivity issues. We are still investigating the issue and will provide an update in 1 hour.
- monitoring · Jun 09, 2026, 05:22 PM UTC
We have identified the issue, have rolled out a fix and are monitoring the situation.
- monitoring · Jun 09, 2026, 05:24 PM UTC
We are continuing to monitor for any further issues.
- resolved · Jun 09, 2026, 05:33 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 3 updates
- identified · May 13, 2026, 04:23 PM UTC
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.
- identified · May 13, 2026, 04:38 PM UTC
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.
- resolved · May 13, 2026, 04:46 PM UTC
The incident has been resolved, and all alerts counts are once again accurate. No customer data was lost, and SOC operations were not impacted.
Latest: The incident has been resolved, and all alerts counts are once again accurate. No customer data was lost, and SOC operations were not impacted.
-
- Alert ingestion
Timeline · 3 updates
- investigating · May 01, 2026, 06:50 PM UTC
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.
- monitoring · May 01, 2026, 07:09 PM UTC
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.
- resolved · May 01, 2026, 08:01 PM UTC
The incident has been resolved, and all systems are once again fully available. No customer data was lost, and all previously-accessible security devices are once again accessible and ingesting alerts.
Latest: The incident has been resolved, and all systems are once again fully available. No customer data was lost, and all previously-accessible security devices are once again accessible …
-
- EmailSlack
Timeline · 2 updates
- investigating · Apr 25, 2026, 05:42 PM UTC
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.
- resolved · Apr 25, 2026, 06:09 PM UTC
This issue has been resolved. All notifications in the backlog have been delivered and new notifications are being delivered as normal.
Latest: This issue has been resolved. All notifications in the backlog have been delivered and new notifications are being delivered as normal.
-
- Alert ingestion
Timeline · 9 updates
- investigating · Apr 20, 2026, 04:20 PM UTC
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.
- investigating · Apr 20, 2026, 05:00 PM UTC
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.
- investigating · Apr 20, 2026, 05:35 PM UTC
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.
- investigating · Apr 20, 2026, 06:01 PM UTC
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.
- identified · Apr 20, 2026, 06:34 PM UTC
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.
- identified · Apr 20, 2026, 07:02 PM UTC
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.
- monitoring · Apr 20, 2026, 07:34 PM UTC
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.
- monitoring · Apr 20, 2026, 08:01 PM UTC
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.
- resolved · Apr 20, 2026, 08:54 PM UTC
We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We investigated the remaining unhealthy devices, which are not related to the customer secrets vault upgrade. This incident is resolved.
Latest: We restored the credentials for the subset of devices, and are seeing that the majority of devices have returned to a healthy state. We investigated the remaining unhealthy devices…
-
See the full Expel outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Expel outage history →Or sign up free to get alerts when Expel breaks · 10 free monitors · No credit card
- Workbench Availability ResolvedStarted Jun 09, 2026, 03:40 PM UTC · Resolved Jun 09, 2026, 05:33 PM UTC · 1h 53m
- Started May 13, 2026, 04:23 PM UTC · Resolved May 13, 2026, 04:46 PM UTC · 22m
- Started May 01, 2026, 06:50 PM UTC · Resolved May 01, 2026, 08:01 PM UTC · 1h 10m
- Delayed Notifications ResolvedStarted Apr 25, 2026, 05:42 PM UTC · Resolved Apr 25, 2026, 06:09 PM UTC · 27m
- Started Apr 20, 2026, 04:20 PM UTC · Resolved Apr 20, 2026, 08:54 PM UTC · 4h 33m
- Started Mar 24, 2026, 04:58 PM UTC · Resolved Mar 24, 2026, 09:12 PM UTC · 4h 14m