# Cribl: Splunk Single Instance and LB Unexpectedly Closing Connections

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2024-08-15 01:31 UTC · Resolved: 2024-08-15 15:56 UTC · Duration: 14 h
- Updates: 7 · Affected components: AWS US East 1 (Virginia) - Data Plane (Workers), Data Plane (Workers)
- [Vendor status page: https://stspg.io/my8t9mp4gnzm](https://stspg.io/my8t9mp4gnzm)
- [Company: Cribl](https://rewindex.com/company/cribl.md)

## Timeline of updates

- **identified** 2024-08-15 01:31 UTC: The issue has been identified and a fix is being implemented.
- **identified** 2024-08-15 01:33 UTC: Status: We have identified an issue in Stream version 4.8.0, where Splunk Single Instance and Splunk Load Balanced Destinations mistakenly detected that the downstream Splunk instance is frequently shutting down. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 minutes. Cribl Support is available to answer questions via email at support@cribl.io. Thank You for being a Cribl.Cloud customer.
- **identified** 2024-08-15 03:25 UTC: Status: We're continuing to review the issue and are working to address it as soon as possible. To mitigate the issue in the meantime, set S2S version to v4. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide an update tomorrow morning at 8 AM EDT (Aug 15). Cribl Support is available to answer questions via email at support@cribl.io.
- **identified** 2024-08-15 12:16 UTC: Status: We have identified a fix and plan on making it available today, within the next few hours. To mitigate the issue in the meantime, set S2S version to v4. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- **identified** 2024-08-15 13:20 UTC: Status: We have started to roll out the fix to addresss the issue. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- **identified** 2024-08-15 15:12 UTC: Status: We're continuing to roll out the fix to addresss the issue. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- **resolved** 2024-08-15 15:56 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2024-08-15 01:31 UTC: [Critical incident: Splunk Single Instance and LB Unexpectedly Closing Connections](https://rewindex.com/change/i2be205eb483537.md)


---
Canonical: https://rewindex.com/company/cribl/incidents/7gh08jrncpz8 · Markdown: https://rewindex.com/company/cribl/incidents/7gh08jrncpz8.md · JSON: https://rewindex.com/api/v1/companies/cribl/incidents/7gh08jrncpz8 · Generated 2026-10-20T00:10:08.259Z