Expel Outage History

Expel is up right now

There were 6 Expel outages since February 2, 2026 totaling 13h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.expel.io

Major May 1, 2026

Security Device Credentials Availability

Detected by Pingoru
May 01, 2026, 06:50 PM UTC
Resolved
May 01, 2026, 08:01 PM UTC
Duration
1h 10m
Affected: Alert ingestion
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Minor April 25, 2026

Delayed Notifications

Detected by Pingoru
Apr 25, 2026, 05:42 PM UTC
Resolved
Apr 25, 2026, 06:09 PM UTC
Duration
27m
Affected: EmailSlack
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Major April 20, 2026

Alert ingestion delayed for a subset of security devices

Detected by Pingoru
Apr 20, 2026, 04:20 PM UTC
Resolved
Apr 20, 2026, 08:54 PM UTC
Duration
4h 33m
Affected: Alert ingestion
Timeline · 9 updates
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

Read the full incident report →

Critical March 24, 2026

Workbench Unable To Deliver Microsoft Teams Notifications

Detected by Pingoru
Mar 24, 2026, 04:58 PM UTC
Resolved
Mar 24, 2026, 09:12 PM UTC
Duration
4h 14m
Affected: Teams
Timeline · 4 updates
  1. investigating Mar 24, 2026, 04:58 PM UTC

    Notifications are currently not being delivered to Microsoft Teams since 4pm UTC. We are actively investigating to determine and address the root cause. We advise you login to Workbench for timely updates and/or to engage with Expel's SOC until the issue is resolved. Updates will be shared as soon as they are available. We will provide an update by 5:30pm UTC.

  2. identified Mar 24, 2026, 05:49 PM UTC

    Update: We have confirmed there are no technical issues with Workbench or with our third party systems that support notifications. Microsoft has since updated its Teams service health to indicate they are investigating a possible issue. We recommend you check your MSFT 365 service health and Microsoft's status page for updates: https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect Until further notice, please continue to login to Workbench for timely updates and/or to engage with Expel's SOC. We will provide notice when Workbench notifications to Teams are operational.

  3. monitoring Mar 24, 2026, 09:02 PM UTC

    Update: We are observing a broad recovery in MS Teams message delivery as of 19:10 UTC. However, Microsoft has confirmed that service remains degraded for some users in the West United States region due to ongoing infrastructure optimizations. We are continuing to monitor the situation. Any messages delayed during this incident are being automatically reprocessed for delivery.

  4. resolved Mar 24, 2026, 09:12 PM UTC

    Resolved: Microsoft has confirmed that the issues affecting Teams bots and message delivery are now fully resolved. All delayed messages have been reprocessed and delivered. Service is operating normally.

Read the full incident report →

Minor March 2, 2026

Alert Ingestion Outage for AWS GuardDuty

Detected by Pingoru
Mar 02, 2026, 06:35 PM UTC
Resolved
Mar 02, 2026, 08:36 PM UTC
Duration
2h
Affected: Alert ingestion
Timeline · 3 updates
  1. monitoring Mar 02, 2026, 06:35 PM UTC

    We are currently monitoring an outage affecting the AWS GuardDuty service. As a result of this outage, our integration with AWS GuardDuty is currently reporting as unhealthy. We will provide an update within 60 minutes, or as soon as more information is available.

  2. monitoring Mar 02, 2026, 07:36 PM UTC

    We are working on a workaround that will bypass the faulty AWS region in order resume alert ingestion from healthy regions. Once the outage in the faulty region is over, we will resume ingestion in that region. We will provide an update within 60 minutes, or as soon as more information is available.

  3. resolved Mar 02, 2026, 08:36 PM UTC

    Workaround is in place, we are bypassing the faulty AWS region and all impacted devices have resumed ingestion. Once the outage in the faulty region is over, we will resume ingestion in that region. Alert Ingestion issue resolved.

Read the full incident report →

Critical February 2, 2026

Workbench Outbound Notifications Delay

Detected by Pingoru
Feb 02, 2026, 09:00 PM UTC
Resolved
Feb 02, 2026, 10:33 PM UTC
Duration
1h 32m
Affected: EmailSlackTeamsTicketing systems (via email, such as Jira)PagerDutyOpsgenie
Timeline · 6 updates
  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.

Read the full incident report →

Looking to track Expel downtime and outages?

Pingoru polls Expel's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Expel reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Expel alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Expel for free

5 free monitors · No credit card required