# Cribl: Major incident: Some S3 destinations are experiencing issues

**Summary:** _summary pending_
- Kind: Major incident · Label: major (vendor)
- Changed: 2025-08-13 16:15 UTC · Detected: 2026-10-19 18:33 UTC
- [Source: https://stspg.io/2qr1tvqg6yb3](https://stspg.io/2qr1tvqg6yb3)
- [Company: Cribl](https://rewindex.com/company/cribl.md)
- Versions: before (none: first archived) → after incident\_version:731/7txpg04j1m5m@919c963e5275
- Change 1 of 1 for this incident

Incident page (full timeline): [Some S3 destinations are experiencing issues](https://rewindex.com/company/cribl/incidents/7txpg04j1m5m.md)
## What changed

**1. Added: Title**

```diff
+ Some S3 destinations are experiencing issues
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2025-08-13 16:15 UTC
```

**5. Added: Resolved time**

```diff
+ 2025-08-15 16:01 UTC
```

**6. Added: Update** (identified) · 2025-08-13 16:15 UTC

```diff
+ The issue has been identified and a fix is being implemented.
```

**7. Added: Update** (identified) · 2025-08-13 16:29 UTC

```diff
+ The following issues with the Amazon S3 Destination are currently being investigated: S3 buckets with 'Object Lock' enabled will fail and S3 Destinations configured without a region set may experience issues.
```

**8. Added: Update** (identified) · 2025-08-13 18:35 UTC

```diff
+ We are currently and testing the fix to the S3 destination issues with object locks enabled and when region is not specified.
```

**9. Added: Update** (monitoring) · 2025-08-13 19:27 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**10. Added: Update** (monitoring) · 2025-08-13 19:32 UTC

```diff
+ We have identified the root cause for both "S3 buckets object lock" and "region is not specified" errors. Both issues were  mitigated for Cloud workers. Please check S3 destination statuses for Hybrid Worker Groups and Edge Nodes, that have been upgraded for 4.13.1, to verify whether S3 destinations are impacted by this issue.
```

**11. Added: Update** (monitoring) · 2025-08-13 19:33 UTC

```diff
+ We have identified the root cause for both "S3 buckets object lock" and "region is not specified" errors. Both issues were  mitigated for Cloud workers. Please check S3 destination statuses for Hybrid Worker Groups and Edge Nodes, that have been upgraded for 4.13.1, to verify whether S3 destinations are impacted by this issue.
```

**12. Added: Update** (monitoring) · 2025-08-14 04:31 UTC

```diff
+ Customers who use AWS SQS sources may experience S3 bucket ingestion issues for buckets that are located in a different geographic region than the SQS queue. This issue has been mitigated for Cloud Workers. We do not recommend upgrading Hybrid Workers to 4.13.1 at this time.
```

**13. Added: Update** (monitoring) · 2025-08-14 17:19 UTC

```diff
+ We will perform a critical upgrade to Cribl Cloud organizations between 09:00 and 12:00 UTC on Friday, August 15th, 2025. An email has been sent to Cribl Cloud users with full details. If you have not yet enabled auto-upgrade on your Hybrid Workers, please manually upgrade them to 4.13.2 once your organization has been upgraded.
```

**14. Added: Update** (resolved) · 2025-08-15 16:01 UTC

```diff
+ This incident has been resolved.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2025-08-13 16:15 UTC | Major incident: Some S3 destinations are experiencing issues (this change) | major |

All Cribl changes: [timeline](https://rewindex.com/company/cribl/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/idfeb94b34f2d34 · Markdown: https://rewindex.com/change/idfeb94b34f2d34.md · JSON: https://rewindex.com/api/v1/changes/idfeb94b34f2d34 · Generated 2026-10-20T00:00:38.417Z