CoreWeave Outage History

CoreWeave is up right now

CoreWeave had 13 outages in the last 2 years totaling 196h 6m of downtime — averaging 0.5 incidents per month.

There were 13 CoreWeave outages since April 28, 2026 totaling 196h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.coreweave.com

Minor June 17, 2026

Cloud Console Access Services Incident

Detected by Pingoru
Jun 17, 2026, 07:23 PM UTC
Resolved
Jun 17, 2026, 09:07 PM UTC
Duration
1h 44m
Affected: CoreWeave CloudCoreWeave Networking (GLOBAL)
Timeline · 2 updates
  1. identified Jun 17, 2026, 07:23 PM UTC

    Hello, We are currently investigating an issue affecting access to the CoreWeave Cloud Console (https://console.coreweave.com). Customers may be unable to log in to or load the Console at this time. Our team is actively investigating and working to restore service as quickly as possible. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue. — CoreWeave Support

  2. monitoring Jun 17, 2026, 07:39 PM UTC

    Hello, We believe the issue has been mitigated. Customers should now be able to access the CoreWeave Cloud Console, authenticate through OIDC and SAML providers, and obtain credentials for CAIOS workloads as expected. Our team is continuing to monitor the environment closely to ensure service stability. We appreciate your patience and apologize for any inconvenience caused by this incident. — CoreWeave Support

Read the full incident report →

Minor June 10, 2026

Service Degradation in US-EAST-04B

Detected by Pingoru
Jun 10, 2026, 01:22 PM UTC
Resolved
Jun 10, 2026, 01:43 PM UTC
Duration
20m
Affected: CoreWeave CloudCoreWeave InfrastructureCoreweave Network (US-EAST-04)
Timeline · 1 update
  1. investigating Jun 10, 2026, 01:22 PM UTC

    We are investigating a service degradation in the US-EAST-04B region that may result in loss of connectivity to the cluster. As the situation evolves, we will continue to provide updates. If you have any questions, please contact [email protected]. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue as quickly as possible.

Read the full incident report →

Minor June 9, 2026

Service Degradation Across Multiple Regions

Detected by Pingoru
Jun 09, 2026, 05:50 PM UTC
Resolved
Jun 09, 2026, 07:44 PM UTC
Duration
1h 54m
Affected: CoreWeave InfrastructureCoreweave Network (US-EAST-04)Coreweave Network (US-EAST-06)Coreweave Network (US-EAST-13)Coreweave Network (US-WEST-01)Coreweave Network (US-WEST-04)Coreweave Network (US-WEST-09)Coreweave Network (EU-SOUTH-04)Coreweave Network (US-WEST-10)Coreweave Network (US-EAST-14)
Timeline · 3 updates
  1. investigating Jun 09, 2026, 05:50 PM UTC

    We are investigating a service degradation in various regions, primarily affecting rtxp6000-8x GPUs, resulting in loss of connectivity to the cluster. As the situation evolves, we will continue to provide updates. If you have any questions, please contact [email protected]. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue as quickly as possible.

  2. identified Jun 09, 2026, 06:05 PM UTC

    We have narrowed down the scope of impact to only RTX Pro 6000 nodes. The issue has been identified as a deployment change that interacted unexpectedly with RTX Pro 6000 based capacity. We are actively working on a fix for this issue.

  3. monitoring Jun 09, 2026, 07:03 PM UTC

    We believe the issue has been mitigated, and we are continuing to monitor the affected services. If you are experiencing an issue or have any further questions please reach out to [email protected].

Read the full incident report →

Minor June 3, 2026

Service Degradation in US-EAST-12A

Detected by Pingoru
Jun 03, 2026, 03:59 PM UTC
Resolved
Jun 03, 2026, 11:51 PM UTC
Duration
7h 52m
Affected: CoreWeave ServicesCoreweave Network (US-EAST-12A)
Timeline · 2 updates
  1. investigating Jun 03, 2026, 03:59 PM UTC

    We are investigating a service degradation in the US-EAST-12A region that may result in loss of connectivity to the cluster. As the situation evolves, we will continue to provide updates. If you have any questions, please contact [email protected]. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue as quickly as possible.

  2. monitoring Jun 03, 2026, 04:43 PM UTC

    Hello, We believe the issue has been mitigated, and we are continuing to monitor the affected services. During our investigation into the potential service degradation in the US-EAST-12A region, no impact to customer connectivity or running workloads was observed. If you are experiencing an issue or have any further questions, please reach out to [email protected]. Thank You, CoreWeave Support team

Read the full incident report →

Minor June 3, 2026

Object Storage and Cluster services Incident

Detected by Pingoru
Jun 03, 2026, 01:29 AM UTC
Resolved
Jun 03, 2026, 03:30 AM UTC
Duration
2h
Affected: CoreWeave Object StorageCoreWeave ServicesCoreweave Network (US-CENTRAL-06)CoreWeave Logging (US-WEST-10)
Timeline · 4 updates
  1. investigating Jun 03, 2026, 01:29 AM UTC

    We are investigating an issue affecting object storage and cluster services in US-CENTRAL-06 and US-WEST-10. As the situation evolves, we will continue to provide our customers with updates on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

  2. identified Jun 03, 2026, 02:17 AM UTC

    Our team has identified the issue and is working to restore services in the affected regions. We will provide a further update once services have been stabilized and restored.

  3. identified Jun 03, 2026, 02:44 AM UTC

    Services in US-CENTRAL-06 have been restored at this time. Our team continues to work on restoring services in US-WEST-10. We will provide an update once services have been restored in US-WEST-10.

  4. monitoring Jun 03, 2026, 03:01 AM UTC

    We believe the issue has been mitigated in US-WEST-10, and we are continuing to monitor services in both regions. If you are experiencing an issue or have any further questions please reach out to [email protected].

Read the full incident report →

Minor June 1, 2026

Service Degradation in US-WEST-04A

Detected by Pingoru
Jun 01, 2026, 04:46 PM UTC
Resolved
Jun 01, 2026, 11:25 PM UTC
Duration
6h 38m
Affected: CoreWeave ServicesCoreweave Network (US-WEST-04)
Timeline · 1 update
  1. investigating Jun 01, 2026, 04:46 PM UTC

    We are investigating a service degradation affecting the US-WEST-04A region, which may result in intermittent storage I/O timeouts and loss of connectivity to the cluster. As the situation evolves, we will continue to provide updates. If you have any questions, please contact [email protected]. We apologize for any inconvenience this may cause and appreciate your patience while we work to resolve the issue as quickly as possible.

Read the full incident report →

Minor May 29, 2026

Object Storage incident in US-WEST-04

Detected by Pingoru
May 29, 2026, 05:29 AM UTC
Resolved
May 29, 2026, 10:40 PM UTC
Duration
17h 11m
Affected: CoreWeave Object StorageCoreweave Network (US-WEST-04)
Timeline · 3 updates
  1. investigating May 29, 2026, 05:29 AM UTC

    We are investigating an issue with Object Storage services in US-WEST-04. As the situation evolves, we will continue to provide our customers with updates on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

  2. investigating May 29, 2026, 05:31 AM UTC

    We are continuing to investigate issues affecting Object storage services in US-WEST-04. As the situation evolves, we will continue to provide our customers with updates on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

  3. monitoring May 29, 2026, 06:01 AM UTC

    We believe the issue has been mitigated, and we are continuing to monitor the affected services. If you are experiencing an issue or have any further questions please reach out to [email protected].

Read the full incident report →

Minor May 21, 2026

Degraded Kubernetes API Server Availability in US-East-01A

Detected by Pingoru
May 21, 2026, 04:18 PM UTC
Resolved
May 21, 2026, 07:26 PM UTC
Duration
3h 8m
Affected: CoreWeave InfrastructureCoreweave Network (US-EAST-01)
Timeline · 2 updates
  1. identified May 21, 2026, 04:18 PM UTC

    Hello, We are actively investigating an issue impacting the availability of the Kubernetes API server across the US-EAST-01A zone. Customers in this zone may be experiencing intermittent or failed connections to their cluster API endpoints. We will keep you posted with updates. Please reach out to [email protected] for any questions . Thank you for your patience as we address it Thank You, CoreWeave Support

  2. monitoring May 21, 2026, 05:17 PM UTC

    Hello team, The issue impacting Kubernetes API server availability in US-EAST-01A has been mitigated, and connectivity has been restored. Our engineering teams are continuing to monitor closely to confirm stability. Thank you for your patience throughout this event. Please reach out to support@coreweave for assistance and any questions

Read the full incident report →

Minor May 20, 2026

US-CENTRAL-08A Incident Kickoff - Investigating

Detected by Pingoru
May 20, 2026, 12:48 PM UTC
Resolved
May 20, 2026, 01:01 PM UTC
Duration
13m
Affected: CoreWeave CloudCoreWeave InfrastructureCoreWeave Infrastructure (US-CENTRAL-08)
Timeline · 1 update
  1. investigating May 20, 2026, 12:48 PM UTC

    We are investigating a facilities issue in US-CENTRAL-08A that is causing node issues. As the situation evolves, we will continue to provide our customers with updates on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

Read the full incident report →

Minor May 11, 2026

Missing Data in Cloud Console

Detected by Pingoru
May 11, 2026, 09:19 PM UTC
Resolved
May 11, 2026, 10:11 PM UTC
Duration
51m
Affected: CoreWeave CloudCoreweave Network (GLOBAL)
Timeline · 2 updates
  1. investigating May 11, 2026, 09:19 PM UTC

    We are investigating issues with the Cloud Console causing resources to not be displayed. This issue is isolated to the UI and would not affect customer workloads. As the situation evolves, we will continue to provide our customers with updates on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

  2. monitoring May 11, 2026, 09:35 PM UTC

    We believe the issue has been mitigated, and we are continuing to monitor the Cloud Console for any further issues. If you are experiencing an issue or have any further questions please reach out to [email protected].

Read the full incident report →

Minor May 11, 2026

Degraded CoreWeave AI Object Storage (CAIOS) Performance in US-East-08A

Detected by Pingoru
May 11, 2026, 03:33 PM UTC
Resolved
May 14, 2026, 07:21 PM UTC
Duration
3d 3h
Affected: CoreWeave Object StorageCoreweave Network (US-EAST-08)
Timeline · 2 updates
  1. identified May 11, 2026, 03:33 PM UTC

    Hello, We are currently investigating reports of degraded performance for CoreWeave AI Object Storage (CAIOS) in US-EAST-08A. Customers may observe: - Elevated HTTP 500 / 503 SlowDown responses on PUT and GET requests - Reduced write throughput - Increased request latency As the situation evolves, we will continue to update our customers on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank You, CoreWeave Support Team.

  2. monitoring May 12, 2026, 10:33 PM UTC

    Hello, The issue has been mitigated. Read and write performance has returned to baseline, and affected workloads should now operate normally. Our storage team continues to monitor to prevent recurrence. If you have any questions, please reach out to us by email: [email protected]. Thank you for your patience during this window. Thank You, CoreWeave Support Team.

Read the full incident report →

Minor April 28, 2026

Object Storage Incident

Detected by Pingoru
Apr 28, 2026, 03:19 AM UTC
Resolved
May 01, 2026, 12:46 AM UTC
Duration
2d 21h
Affected: CoreWeave Object StorageCoreweave Network (US-EAST-04)
Timeline · 3 updates
  1. investigating Apr 28, 2026, 03:19 AM UTC

    Hello, We are actively investigating an issue that may be impacting our object storage services. Requests to object storage may encounter 5XX responses or timeouts. As the situation evolves, we will continue to update our customers on the matter. If you have any questions, we encourage you to reach out to support by email: [email protected] We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

  2. identified Apr 28, 2026, 04:06 AM UTC

    We have identified the root cause of the issue and are actively working on a resolution at this time.

  3. monitoring Apr 28, 2026, 05:54 AM UTC

    We believe the issue has been mitigated, and we are continuing to monitor the affected services. If you are experiencing an issue or have any further questions please reach out to [email protected].

Read the full incident report →