Between 29 October 2025, 15:45 UTC and 30 October 2025, 03:45 UTC 2025, customers using the Outgoing Webhook (Impressions) integration experienced delays in receiving impression data.
A small subset of customers hosted on Microsoft Azure would have stopped receiving impression events due to persistent failures on their side to receive these events. Still, those customers can export data from our platform.
All other services, including APIs and SDKs, remained fully operational.
During the Microsoft Azure outage, customers hosted on Azure experienced persistent delivery failures for their impression events. These repeated retries resulted in longer processing times in our webhook delivery system, which in turn caused delays for other customers whose destinations were not impacted.
We initially chose to wait before stopping deliveries to the affected Azure customers. Once we confirmed the issue’s scope, we temporarily paused deliveries to the failing destinations, allowing delivery for all other customers to recover quickly.
Customers whose deliveries were paused can still retrieve their impression events for the impact window by exporting them directly from our platform. We also resumed sending events to all of our customers right after the Azure outage was mitigated.
| Time (UTC) | Event Description |
|---|---|
| 29/10/2025 15:45:00 UTC | Azure goes down; internal monitoring alerts delays in delivering webhook events to customers. |
| 29/10/2025 16:15:00 UTC | On-call paged. |
| 29/10/2025 16:55:00 UTC | Root cause identified as an ongoing Azure outage. |
| 29/10/2025 19:42:00 UTC | Signs of recovery in Azure system; delay starts to decrease, and response times improve. |
| 29/10/2025 22:40:00 UTC | Blocked 100% of webhook traffic to one failing customer to speed recovery. |
| 30/10/2025 01:15:00 UTC | Azure incident declared fully remediated. |
| 30/10/2025 03:45:00 UTC | Resumed delivering webhook impression events to all customers; internal monitoring confirmed restoration of real-time delivery. Incident closed. |
We initially waited for the affected Azure-hosted customers to recover as the Azure outage progressed. However, to maintain timely delivery for all other customers, we temporarily paused event deliveries to a small number of endpoints that continued to experience failures. Once Azure services stabilized, we resumed normal delivery to all customers before closing the incident.