- Detected by Pingoru
- May 13, 2026, 04:23 PM UTC
- Resolved
- May 13, 2026, 04:46 PM UTC
- Duration
- 22m
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
-
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.
Read the full incident report →
- 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
Read the full incident report →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 - 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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 →
Critical January 20, 2026 - Detected by Pingoru
- Jan 20, 2026, 08:31 PM UTC
- Resolved
- Jan 20, 2026, 11:02 PM UTC
- Duration
- 2h 30m
Affected: Alert ingestion
Timeline · 3 updates
-
investigating Jan 20, 2026, 08:31 PM UTC
At 3:00pm ET, we began experiencing a problem with alert ingestion. We will provide an update by 4:30pm ET.
-
monitoring Jan 20, 2026, 08:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 20, 2026, 11:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2026, 07:51 PM UTC
- Resolved
- Jan 07, 2026, 10:54 PM UTC
- Duration
- 3h 2m
Timeline · 4 updates
-
investigating Jan 07, 2026, 07:51 PM UTC
Starting 1/6/25 at roughly 12:00 EST, we have identified an issue with our phishing service where outcome emails are being sent multiple times to some users and are investigating the root cause. Ingestion and email review are not affected. We will provide an update at 4pm EST.
-
identified Jan 07, 2026, 09:11 PM UTC
We believe we have identified the root cause of duplicate phishing outcome emails and are preparing a hotfix. Next update at 5pm EST.
-
monitoring Jan 07, 2026, 10:00 PM UTC
The hotfix for duplicate phishing outcomes has been deployed and we are monitoring. Next update at 6pm EST.
-
resolved Jan 07, 2026, 10:54 PM UTC
The hotfix for phishing submission outcome emails was successful and behavior has returned to normal. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 29, 2025, 09:26 PM UTC
- Resolved
- Dec 29, 2025, 10:09 PM UTC
- Duration
- 42m
Affected: Alert ingestion
Timeline · 3 updates
-
investigating Dec 29, 2025, 09:26 PM UTC
At 3:17, we began experiencing a problem with enrichment service that is impacting detections. We will provide an update by 4:45.
-
monitoring Dec 29, 2025, 09:49 PM UTC
We have identified and implemented a fix and are monitoring; service queues are approaching normal.
-
resolved Dec 29, 2025, 10:09 PM UTC
Detection pipelines are caught up. Service is nominal.
Read the full incident report →
Critical November 18, 2025 - Detected by Pingoru
- Nov 18, 2025, 03:34 PM UTC
- Resolved
- Nov 19, 2025, 06:17 PM UTC
- Duration
- 1d 2h
Affected: Teams
Timeline · 3 updates
-
identified Nov 18, 2025, 03:34 PM UTC
Workbench cannot currently deliver notifications to Microsoft Teams. The issue began around 9:45am ET. Expel is actively investigating the issue to determine if it is related to the larger Cloudflare outage. We recommend you utilize email notifications in the interim, and can confirm communicating with Expel personnel via Microsoft Teams still works. The issue is specific to Workbench notifications.
-
monitoring Nov 18, 2025, 03:50 PM UTC
The underlying issue has been resolved We are monitoring the health of the infrastructure and will resolve this if there are no outstanding issues. Please let us know if you are experiencing any problems.
-
resolved Nov 19, 2025, 06:17 PM UTC
This incident has been resolved.
Read the full incident report →
Critical November 12, 2025 - Detected by Pingoru
- Nov 12, 2025, 03:28 PM UTC
- Resolved
- Apr 17, 2026, 01:52 PM UTC
- Duration
- 155d 22h
Affected: Alert ingestion
Timeline · 2 updates
-
identified Nov 12, 2025, 03:28 PM UTC
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.
-
resolved Apr 17, 2026, 01:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 04:56 PM UTC
- Resolved
- Nov 03, 2025, 07:43 PM UTC
- Duration
- 2h 47m
Affected: Investigative actions
Timeline · 4 updates
-
investigating Nov 03, 2025, 04:56 PM UTC
At 10:50am ET, we began experiencing a problem with pivoting to Wiz console that resulting in some degraded analyst triage experience. We will provide an update by 12:50pm ET.
-
investigating Nov 03, 2025, 05:50 PM UTC
We have reached out to Wiz and waiting to hear back. We will provide an update by 1:50pm ET.
-
monitoring Nov 03, 2025, 06:55 PM UTC
Analysts are starting to successfully SSO into the Wiz console. We will continue to monitor the situation. We will provide an update by 3:00pm ET.
-
resolved Nov 03, 2025, 07:43 PM UTC
Analysts are able to successfully SSO into the Wiz console. Incident is closed.
Read the full incident report →
- Detected by Pingoru
- Oct 29, 2025, 05:17 PM UTC
- Resolved
- Oct 30, 2025, 02:22 AM UTC
- Duration
- 9h 5m
Affected: Investigative actionsAlert ingestion
Timeline · 7 updates
-
identified Oct 29, 2025, 05:17 PM UTC
Microsoft has reported an outage affecting O365 services. As a result of this outage, our integration with O365 is currently reporting as unhealthy. We are actively monitoring this issue and will provide an update within 60 minutes, or as soon as more information is available.
-
identified Oct 29, 2025, 06:13 PM UTC
Microsoft has reported an outage affecting O365 services. As a result of this outage, our integration with O365 is currently reporting as unhealthy. We are actively monitoring this issue and will provide an update within 60 minutes, or as soon as more information is available.
-
identified Oct 29, 2025, 07:09 PM UTC
Microsoft has reported an outage affecting O365 services. As a result of this outage, our integration with O365 is currently reporting as unhealthy. We are actively monitoring this issue and will provide an update within 60 minutes, or as soon as more information is available.
-
identified Oct 29, 2025, 08:09 PM UTC
Microsoft has reported an outage affecting O365 services. As a result of this outage, our integration with O365 is currently reporting as unhealthy. We are actively monitoring this issue and will provide an update within 60 minutes, or as soon as more information is available.
-
monitoring Oct 29, 2025, 08:59 PM UTC
Our integration with O365 has become healthy. We are currently ingesting and processing a backlog of events and will provide another update in 60 minutes.
-
monitoring Oct 29, 2025, 09:57 PM UTC
Our integration with O365 has become healthy and the backlog of events have been processed. We will continue to monitor the O365 service outage and will provide updates as they come.
-
resolved Oct 30, 2025, 02:22 AM UTC
Microsoft has confirmed that the O365 outage has been completely resolved. Our integration with O365 remains healthy and no customer data was lost.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:41 PM UTC
- Resolved
- Oct 21, 2025, 04:59 AM UTC
- Duration
- 9h 18m
Affected: Workbench loginAlert ingestion
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 10:06 AM UTC
- Resolved
- Oct 20, 2025, 12:35 PM UTC
- Duration
- 2h 28m
Affected: EmailSlackTeamsTicketing systems (via email, such as Jira)Alert ingestionPagerDutyOpsgenie
Timeline · 7 updates
-
monitoring Oct 20, 2025, 10:06 AM UTC
Amazon Web Services reported an outage affecting AWS services in the US-EAST-1 region starting at approximately 06:50am UTC. AWS communicated that it identified the root cause and took mitigation actions, and that it’s seeing significant signs of recovery. This outage is affecting how Expel Workbench ingests and processes alerts, as well as how we communicate with customers. At this time, Expel Workbench is operating normally. Our systems are working through a backlog of security device data.
-
monitoring Oct 20, 2025, 10:33 AM UTC
We are continuing to monitor. Workbench is working the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:00am UTC.
-
monitoring Oct 20, 2025, 11:04 AM UTC
We are continuing to monitor. Workbench continues to process the backlog of alerts. Amazon reports that it has mitigated the underlying the DNS issue, and most AWS Service operations are succeeding normally now. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 11:30am UTC.
-
monitoring Oct 20, 2025, 11:31 AM UTC
We are continuing to monitor. Workbench continues to process the backlog of alerts. Please note that no customer data was lost as a result of the AWS outage. We will post the next update at 12:00pm UTC.
-
monitoring Oct 20, 2025, 11:59 AM UTC
Expel Workbench is fully operational, has processed the full backlog of alerts, and is ingesting and processing current alerts normally. We will continue to monitor and provide additional updates as necessary.
-
monitoring Oct 20, 2025, 12:24 PM UTC
We are continuing to monitor for any further issues.
-
resolved Oct 20, 2025, 12:35 PM UTC
The incident has been resolved, and all systems are once again fully available. No customer data was lost.
Read the full incident report →
Critical October 17, 2025 - Detected by Pingoru
- Oct 17, 2025, 05:55 AM UTC
- Resolved
- Oct 17, 2025, 06:59 AM UTC
- Duration
- 1h 3m
Affected: Teams
Timeline · 5 updates
-
investigating Oct 17, 2025, 05:55 AM UTC
At 01:09UTC Oct 17th 2025, we began experiencing a problem with an upstream messaging provider that is preventing Workbench from sending automated messages to Microsoft Teams channels. We escalated the incident to the provider. They identified the cause of the problem and are working on a fix. We will provide an update by 06:30am UTC.
-
identified Oct 17, 2025, 05:56 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Oct 17, 2025, 06:13 AM UTC
The upstream provider confirmed that they resolved the problem. Workbench is now successfully sending messages to Microsoft Teams channels. We will continue to monitor as Workbench retries to send messages that failed because of this issue. We will post an update at 06:30UTC.
-
monitoring Oct 17, 2025, 06:32 AM UTC
We are continuing to monitor. Workbench continues to successfully send MS Teams messages. We will post the next update at 07:00am UTC.
-
resolved Oct 17, 2025, 06:59 AM UTC
The incident has been resolved, and all systems are once again fully available. All Microsoft Teams messages from Workbench that failed during the incident have been successfully delivered.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 01:56 PM UTC
- Resolved
- Oct 09, 2025, 02:25 PM UTC
- Duration
- 28m
Timeline · 3 updates
-
investigating Oct 09, 2025, 01:56 PM UTC
At 13:30UTC, we began experiencing a problem with the Alert Analysis Dashboard that is preventing users from seeing metrics on that page only. Alert ingestion & SOC operations are not affected. We will provide an update by 14:30UTC.
-
monitoring Oct 09, 2025, 02:23 PM UTC
We have implemented a fix and believe the incident to be resolved. We are monitoring the health of the infrastructure and will resolve this if there are no outstanding issues. Please let us know if you are experiencing any problems.
-
resolved Oct 09, 2025, 02:25 PM UTC
The incident has been resolved and the Alert Analysis Dashboard is once again fully available. No customer data was lost, and SOC operations were not impacted.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2025, 08:59 AM UTC
- Resolved
- Oct 08, 2025, 10:50 AM UTC
- Duration
- 1h 50m
Affected: EmailSlackTeamsSlack channels for customers
Timeline · 5 updates
-
identified Oct 08, 2025, 08:59 AM UTC
We have identified an issue with a 3rd party vendor that is causing a 10-15 minute delay in sending email, slack and MS Teams notifications from Workbench. Alert ingestion is not affected. Please be aware that this delay applies to all client notifications, such as Verify Actions and New Incident Notifications. There is no other impact to SOC operations. Customers can continue to request support as usual (ticket creation is not affected by this delay).
-
identified Oct 08, 2025, 09:34 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Oct 08, 2025, 09:42 AM UTC
We continue to experience a delay of approximately 10–15 minutes in delivering email, Slack, and Microsoft Teams notifications from Workbench. Our team has escalated the issue with our vendor and is actively monitoring the situation. We’ll provide an update here as soon as we have more information or when service performance returns to normal.
-
monitoring Oct 08, 2025, 10:04 AM UTC
We are no longer observing delays in delivering email, slack and MS Teams notifications from Workbench. We will continue to monitor for the next hour as we work with our vendor to confirm that the issue is resolved.
-
resolved Oct 08, 2025, 10:50 AM UTC
We have confirmed that the incident has been resolved. Email, slack and MS Teams notifications from Workbench are being delivered within normal timeframes.
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2025, 01:17 PM UTC
- Resolved
- Sep 09, 2025, 01:34 PM UTC
- Duration
- 16m
Timeline · 3 updates
-
identified Sep 09, 2025, 01:17 PM UTC
There is a known issue with Wiz. This is preventing our ability to triage and investigate Wiz alerts. Wiz have identified the root cause and a fix is being implemented (https://status.wiz.io/). As an interim workaround for impacted customers, we are going to promote/verify any critical or high Wiz alerts that come into the queue
-
identified Sep 09, 2025, 01:22 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Sep 09, 2025, 01:34 PM UTC
Wiz have confirmed that they have resolved the issue and our SOC Analysts are now able to triage and investigate Wiz alerts.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 01:24 AM UTC
- Resolved
- Aug 20, 2025, 06:11 AM UTC
- Duration
- 4h 46m
Affected: Alert ingestion
Timeline · 6 updates
-
investigating Aug 20, 2025, 01:24 AM UTC
We are currently investigating an outage affecting the Azure Security Center API. As a result of this outage, our integration with Azure is currently reporting as unhealthy. We will provide an update within 30 minutes, or as soon as more information is available.
-
investigating Aug 20, 2025, 02:10 AM UTC
We continue to actively investigate the outage affecting the Azure Security Center API. We will provide an update at within 60 minutes, or as soon as more information is available.
-
investigating Aug 20, 2025, 03:03 AM UTC
We continue to actively investigate the outage affecting the Azure Security Center API. We will provide an update at within 60 minutes, or as soon as more information is available.
-
investigating Aug 20, 2025, 04:05 AM UTC
We continue to actively investigate the outage affecting the Azure Security Center API. We will provide an update at within 60 minutes, or as soon as more information is available.
-
investigating Aug 20, 2025, 05:20 AM UTC
We continue to actively investigate the outage affecting the Azure Security Center API. We will provide an update at within two hours, or as soon as more information is available.
-
resolved Aug 20, 2025, 06:11 AM UTC
The outage affecting the Azure Security Center API has been resolved, and all services are now fully operational. Our security alerts and recommendations are flowing as expected, and our integration with Azure is now reporting as healthy. No customer data was lost.
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2025, 06:47 PM UTC
- Resolved
- Aug 11, 2025, 10:44 PM UTC
- Duration
- 3h 57m
Affected: Investigative actionsAlert ingestion
Timeline · 7 updates
-
identified Aug 11, 2025, 06:47 PM UTC
Alert ingestion is currently delayed. We have identified the root cause and are working on a remediation. We will provide another update by 3:30pm EDT.
-
identified Aug 11, 2025, 07:33 PM UTC
Alert ingestion is still delayed. We have identified the root cause and are working on a remediation. We will provide another update by 4:00pm EDT.
-
identified Aug 11, 2025, 08:05 PM UTC
Alert ingestion is still delayed. We have identified the root cause and are working on a remediation. We will provide another update by 4:30pm EDT.
-
identified Aug 11, 2025, 08:43 PM UTC
Alert ingestion is still delayed. We have encountered further issues and are working on identifying the root cause. We will provide another update by 5:30pm EDT.
-
identified Aug 11, 2025, 09:50 PM UTC
Alert ingestion is still delayed. We have taken steps to mitigate the issue and are monitoring to ensure recovery. We will provide another update by 6:30pm EDT.
-
monitoring Aug 11, 2025, 10:30 PM UTC
Alert ingestion is still delayed but catching up. We have taken steps to mitigate the issue and are monitoring to ensure recovery. We will provide another update by 7:00pm EDT.
-
resolved Aug 11, 2025, 10:44 PM UTC
Alert ingestion has caught up and is no longer delayed. This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 10:45 AM UTC
- Resolved
- Aug 08, 2025, 04:07 PM UTC
- Duration
- 5h 21m
Affected: Alert ingestion
Timeline · 7 updates
-
investigating Aug 08, 2025, 10:45 AM UTC
At 2am ET, we began experiencing a problem with alert ingestion. SOC operations are affected, but will catch up once service is restored; no data will be lost. We will provide an update by 7:30AM.
-
investigating Aug 08, 2025, 11:23 AM UTC
We are still investigating. We will provide an update by 8:30AM.
-
investigating Aug 08, 2025, 12:22 PM UTC
We are still investigating. We will provide an update by 9:30AM.
-
investigating Aug 08, 2025, 01:26 PM UTC
We are still investigating. We will provide an update by 10:30AM.
-
investigating Aug 08, 2025, 02:17 PM UTC
Root cause still under investigation but system is recovering. We will provide an update by 11:30am.
-
monitoring Aug 08, 2025, 03:26 PM UTC
We have identified the root cause. Alert ingestion is recovering. No customer data was lost. We will provide another update by 12:30pm ET.
-
resolved Aug 08, 2025, 04:07 PM UTC
The incident has been resolved. All systems are once again fully available. No customer data was lost.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2025, 10:32 PM UTC
- Resolved
- Jul 09, 2025, 11:37 PM UTC
- Duration
- 1h 5m
Affected: Alert ingestion
Timeline · 3 updates
-
monitoring Jul 09, 2025, 10:32 PM UTC
We have implemented a fix and believe the incident to be resolved. We are currently processing the backlog. We will provide another update by 7pm ET.
-
monitoring Jul 09, 2025, 11:00 PM UTC
The backlog is still being processed. We will provide another update by 7:30pm ET.
-
resolved Jul 09, 2025, 11:37 PM UTC
The backlog has been processed. The incident has been resolved. No customer data was lost, and SOC operations were not impacted.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 09:51 AM UTC
- Resolved
- Jun 23, 2025, 08:04 PM UTC
- Duration
- 10h 12m
Affected: Assembler connectivityAlert ingestion
Timeline · 12 updates
Read the full incident report →