# Incorrect Delivery for S3 and S3 Datalake

- Provider: [RudderStack](https://down.guide/rudderstack)
- Level: confirmed
- Impact: Degraded
- lasted 2h 15m
- started 2025-05-28 17:00 UTC
- Data Processing Pipeline (US), Warehouses
- us
- id: DWN-407e7b508f
- Official page: https://stspg.io/ny4p69dj2w92

## Updates from RudderStack
### 2025-05-28 17:00 UTC: identified
Issue has been identified with S3 and S3 datalake deliveries. Actively working on the fix.

### 2025-05-28 19:15 UTC: resolved
An issue was identified with the delivery module for S3 & S3\_DATALAKE destinations, leading to the incorrect duplication of the prefix in the final file path. This resulted in data being uploaded to an unintended location, making it unavailable for any downstream consumption for the duration of the incident.
The flag was enabled only for free tier and starter and growth customers.
Follow the below recommended steps to recover the data:
Prerequisite: Make sure the AWS CLI is installed and configured locally to access the relevant S3 bucket.
1. Go to the Rudderstack configuration page of your S3/S3 Datalake destinations and copy bucket name and prefix.
2. Copy all the files from the double-prefix path to the single prefix path.
 Command: aws s3 cp s3://{bucket\_name}/{prefix}/{prefix}/ s3://{bucket\_name}/{prefix}/ --recursive
3. Delete the original files (optional)
 Command:aws s3 rm s3://{bucket\_name}/{prefix}/{prefix}/ --recursive

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).