All Systems Operational

Workbench availability Operational
Workbench global network connectivity Operational
Workbench login Operational
Workbench features Operational
Investigative actions Operational
File uploads Operational
Notifications Operational
Email Operational
Slack Operational
Teams Operational
Ticketing systems (via email, such as Jira) Operational
PagerDuty Operational
Opsgenie Operational
ServiceNow Operational
Assembler connectivity Operational
Alert ingestion Operational
Slack channels for customers Operational
Phishing submissions Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Workbench global network connectivity ?
Fetching
Workbench availability ?
Fetching
May 3, 2026

No incidents reported today.

May 2, 2026

No incidents reported.

May 1, 2026
Security Device Credentials Availability
Resolved - 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.
May 1, 16:01 EDT
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, 15:09 EDT
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, 14:50 EDT
Apr 30, 2026

No incidents reported.

Apr 29, 2026

No incidents reported.

Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026
Delayed Notifications
Resolved - This issue has been resolved. All notifications in the backlog have been delivered and new notifications are being delivered as normal.
Apr 25, 14:09 EDT
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, 13:42 EDT
Apr 24, 2026

No incidents reported.

Apr 23, 2026

No incidents reported.

Apr 22, 2026

No incidents reported.

Apr 21, 2026

No incidents reported.

Apr 20, 2026
Alert ingestion delayed for a subset of security devices
Resolved - 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.
Apr 20, 16:54 EDT
Update - 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, 16:01 EDT
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, 15:34 EDT
Update - 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, 15:02 EDT
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, 14:34 EDT
Update - 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, 14:01 EDT
Update - 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, 13:35 EDT
Update - 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, 13:00 EDT
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, 12:20 EDT
Apr 19, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage