We continue to investigate an issue impacting Data 360 customers who use Bring Your Own Lake (BYOL) with Redshift connections. Additional teams are now engaged to assist with end-to-end validation bef

Update timeline

1. identified Jul 01, 2026, 03:44 PM UTC

   Degradation Started: slowDataProcessing

2. monitoring Jul 01, 2026, 03:57 PM UTC

   We're aware of an issue impacting Data 360 Batch Data Transforms. As a result, customers may be unable to run or complete Batch Data Transform jobs. We're actively investigating and working to restore full functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available.

3. monitoring Jul 01, 2026, 04:25 PM UTC

   We're aware of an issue affecting Data 360 customers using Bring Your Own Lake (BYOL) with Redshift connections. Customers may experience delays in data availability rather than complete job failures, as the Batch Data Transform service includes a retry mechanism. We've identified a network configuration as the likely trigger and have applied a fix that's currently being validated across affected environments. We'll provide an update in 30 minutes or sooner if additional information becomes available.

4. monitoring Jul 01, 2026, 04:55 PM UTC

   We continue to investigate an issue impacting Data 360 customers who use Bring Your Own Lake (BYOL) with Redshift connections. Validation of the network configuration fix is still in progress across all impacted environments. We'll provide an update in 60 minutes or sooner if additional information becomes available.

5. monitoring Jul 01, 2026, 05:57 PM UTC

   We continue to investigate an issue impacting Data 360 customers who use Bring Your Own Lake (BYOL) with Redshift connections. Additional teams are now engaged to assist with end-to-end validation before the fix is rolled out to all remaining impacted environments. We'll provide an update in 60 minutes or sooner if additional information becomes available.