Ingest issues for some customers

Update timeline

1. identified Apr 10, 2026, 01:41 PM UTC

   We have confirmed reports of some teams getting issues ingesting their data. We have identified a probable source behind this behavior and are currently trying to correct it.

2. identified Apr 10, 2026, 01:46 PM UTC

   We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.

3. identified Apr 10, 2026, 01:55 PM UTC

   We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.

4. monitoring Apr 10, 2026, 02:19 PM UTC

   We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.

5. monitoring Apr 10, 2026, 02:32 PM UTC

   The manual fix has been applied to all environments.

6. monitoring Apr 10, 2026, 03:21 PM UTC

   We are continuing to work on the systemic solution and monitor. We'll leave the incident open until we're able to confirm the issue won't recur.

7. resolved Apr 10, 2026, 05:24 PM UTC

   We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.