CoreWeave incident
Object Storage Service Degradation in US-EAST-04
CoreWeave experienced a major incident on June 4, 2026 affecting CoreWeave Premium Shared Filesystem Volumes and CoreWeave Object Storage and 1 more component, lasting 8h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 04, 2026, 06:34 PM UTC
The CoreWeave Object Storage Service is downgraded in US-EAST-04. Customers may experience intermittent request failures. We have identified the root cause and are working on the remediations. If you have any questions, please contact us at [email protected].
- monitoring Jun 04, 2026, 08:18 PM UTC
We have implemented a fix for the issue affecting Object Storage Service in US-EAST-04, and the impacted service is now operational. We are closely monitoring the environment to ensure stability and will post another update if we observe any recurrence or unexpected behavior. If you are still seeing issues, please reach out to [email protected].
- investigating Jun 04, 2026, 11:20 PM UTC
We're investigating additional reports of ongoing issues with request's failing for Object Storage in us-east-04. We'll provide additional updates as we continue our investigation. Thank you for our patience as we continue our investigation.
- investigating Jun 04, 2026, 11:25 PM UTC
We are additionally investigating reports of impact to DFS volumes in addition to latency and request failures to Object Storage.
- investigating Jun 04, 2026, 11:34 PM UTC
We have seen recovery in the availability of DFS services in the region but continue to investigate issues related to performance, and latency with requests to Object Storage in the region.
- investigating Jun 04, 2026, 11:46 PM UTC
We continue to investigate DFS and Object Storage performance issues.
- investigating Jun 05, 2026, 12:24 AM UTC
We continue to investigate performance related issues with Object Storage request latency and failed requests. At this time though we consider the issues affecting DFS's to be mitigated and we continue to monitor the performance closely. We will continue to provide updates as the new information is available.
- identified Jun 05, 2026, 01:30 AM UTC
We believe we have identified the issues affecting latency, and have applied mitigations. We will provide an additional update after a period of monitoring.
- monitoring Jun 05, 2026, 01:47 AM UTC
We believe the issues affecting latency have been resolved, and the impacted service is now operational. We are closely monitoring the environment to ensure stability and will post another update if we observe any recurrence or unexpected behavior prior to resolving. If you are still seeing issues, please reach out to [email protected].