ChangesCriblSome S3 destinations are experiencing issues
Cribl: Major incident: Some S3 destinations are experiencing issues
Summary
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Cribl removed; blue is what they added. Muted text is unchanged context.
Before: not present
After: Some S3 destinations are experiencing issues
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-08-13 16:15 UTC
Before: not present
After: 2025-08-15 16:01 UTC
Before: not present
After: The issue has been identified and a fix is being implemented.
Before: not present
After: 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.
Before: not present
After: We are currently and testing the fix to the S3 destination issues with object locks enabled and when region is not specified.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
Wednesday, August 13, 2025
1 incident change
- MajorMajor incident
Some S3 destinations are experiencing issuesthis change