Datadog US1 incident
Periodic network interruption communicating with multiple Azure regions
Datadog US1 experienced a minor incident on August 28, 2025 affecting APM and Log Management and 1 more component, lasting 1d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 28, 2025, 07:30 PM UTC
Degraded network capacity in an Azure datacenter is causing network packet loss and increased latency when communicating with AWS in eastern US regions. Customers may experience communications failures trying to submit data from agents running in AWS and may experience delayed data from AWS integrations. Microsoft has identified the root cause and is working on mitigations.
- monitoring Aug 28, 2025, 08:37 PM UTC
The root cause of the issue has been identified and Microsoft has implemented mitigations, we are monitoring network traffic to confirm.
- monitoring Aug 29, 2025, 08:47 PM UTC
Azure has temporarily mitigated the network capacity issues which have caused episodic packet loss for customers who are hosted in Azure data centers and are using Datadog’s US1 region (accessible via https://app.datadoghq.com). Azure engineers are continuing to work to fully resolve this issue. Until they fully resolve the issue, customers with Datadog agents running in Azure data centers may see brief periods of delayed ingestion of data from agents and from Azure integrations. We don’t expect a noticeable impact thanks to agent buffering but cannot exclude the possibility of spurious alerts due to temporarily delayed data. We are continuing to monitor the situation in conjunction with Azure, and will do so throughout the weekend. We will post status page updates as soon as the situation improves, and at least every 24 hours. We thank you for your patience throughout this incident.
- monitoring Aug 30, 2025, 03:12 AM UTC
Azure has implemented a permanent fix to the network issue. Both Azure and Datadog engineers are continuing to monitor overnight and will provide an update tomorrow.
- resolved Aug 30, 2025, 06:58 PM UTC
Our monitoring has shown Azure’s fix to be stable since our last update. This incident has been resolved.