CoreWeave incident

Object Storage Performance Degradation in US-WEST-01A

Minor Resolved View vendor source →

CoreWeave experienced a minor incident on August 27, 2026 affecting CoreWeave Object Storage and CoreWeave Networking (US-WEST-01), lasting 17h 19m. The incident has been resolved; the full update timeline is below.

Started
Aug 27, 2026, 03:37 AM UTC
Resolved
Aug 27, 2026, 08:56 PM UTC
Duration
17h 19m
Detected by Pingoru
Aug 27, 2026, 03:37 AM UTC

Affected components

CoreWeave Object StorageCoreWeave Networking (US-WEST-01)

Update timeline

  1. investigating Aug 27, 2026, 03:37 AM UTC

    We are investigating elevated error rates and increased latency for Object Storage in the US-WEST-01A region. Requests to this region may intermittently return HTTP 503 responses or take longer than usual to complete. Our engineering team is actively engaged and working to identify the root cause.

  2. identified Aug 27, 2026, 09:03 AM UTC

    We have identified the issue and are continuing to work on a resolution at this time.

  3. monitoring Aug 27, 2026, 10:49 AM UTC

    We've implemented a fix to address the object storage latency and error codes in US-WEST-01A. All services are now fully operational, and we are monitoring closely to ensure stability. If you continue to see issues, please reach out to [email protected].

  4. investigating Aug 27, 2026, 01:19 PM UTC

    We are investigating renewed elevated error rates and increased latency for object storage in US-WEST-01A. A change applied earlier today improved service for a period, but the degradation has returned and our engineering team is actively engaged and working to identify the root cause. Clients may see intermittent 503 responses.

  5. monitoring Aug 27, 2026, 07:28 PM 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].