Huntress experienced a minor incident on August 31, 2026 affecting ITDR, lasting 20d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 31, 2026, 04:53 PM UTC
We have noticed a slight delay in our ITDR ingestion pipeline, and are investigating the cause.
- identified Aug 31, 2026, 05:37 PM UTC
We've identified that the cause of our ingestion delay is from a degradation in Microsoft's M365 APIs. No GWS customer are affected. We're working through our partner channels to get this resolved, and will update this page as soon as we know more information.
- monitoring Sep 01, 2026, 10:09 PM UTC
We're continuing to work with our partners at Microsoft, who have identified the cause of the delay and are in the process of implementing a fix. We are still seeing intermittent delays of up to 4 hours for some customers. We will continue to provide updates as soon as more information becomes available.
- monitoring Sep 11, 2026, 03:55 PM UTC
We are continuing to provide information about any affected customers to our partners at Microsoft. Intermittent delays continue to show up for a small set of affected customers.
- monitoring Sep 14, 2026, 06:49 PM UTC
We are continuing to work with Microsoft to resolve the intermittent delays for a small set of affected customers.
- monitoring Sep 16, 2026, 02:53 PM UTC
Our partners at Microsoft are in the process of rolling out a fix across the affected tenants. We are monitoring the effect and providing information to them on the effectiveness of this solution.
- monitoring Sep 17, 2026, 03:18 PM UTC
Our partners at Microsoft have deployed a fix for the affected customers which will roll out over the remainder of this week and into the weekend. We will continue working with them to verify the fix is working as intended.
- resolved Sep 20, 2026, 09:18 PM UTC
Microsoft has deployed additional fixes to their infrastructure, and our internal telemetry is back to showing normal ingest timing for events. This incident is now resolved.