Multiple connections with Managed Data Lake Service are failing in AWS region

This incident has been resolved.

We have deployed a fix to rollback and recover affected snapshots to the latest stable version.

Affected connectors are resuming their normal sync functionality and we are continuing to monitor progress.

We are continuing to work on a fix for this issue. We will additionally contact customers directly for resolutions in certain cases.

We are making code changes to roll back to the previous snapshot if the table is found to be corrupted. We will share further updates as soon as more information becomes available.

We are continuing to work on investigating the root cause and a fix for this issue.

We are currently observing sync failures across multiple connectors, with the error "Found conflicting files that can contain records matching".

Our team is actively investigating the root cause of this issue. We will provide further updates as soon as more information becomes available.

We have deployed a fix to reduce the number of retries and also increased the minimum number of ports to help handle the large number of requests. This has lead to a reduction in failures, but some connectors are still affected.

Remaining connectors are still being investigated for intermittent connectivity issues with Polaris.

We are still working on a fix for this issue.

We are continuing to work on a fix for this issue.

We are currently investigating an issue affecting multiple connections, which are failing with the following error:
"org.apache.iceberg.exceptions.RESTException: Unable to process: Failed to get subscoped credentials: Unable to execute HTTP request, Connect timed out"

The issue has been identified and we are working to resolve it.