- Detected by Pingoru
- Aug 02, 2026, 01:08 AM UTC
- Resolved
- Aug 02, 2026, 03:42 AM UTC
- Duration
- 2h 34m
Affected: CoreWeave Object StorageCoreWeave Cloud Console (GLOBAL)
Timeline · 2 updates
-
identified Aug 02, 2026, 01:08 AM UTC
We have identified the root cause of the issue and are actively working on a fix. We will update you when we have pushed a fix.
-
identified Aug 02, 2026, 01:23 AM UTC
We have identified the cause of an issue affecting Object Storage access key creation globally. Customers using SAML or OIDC-based access key creation may currently be unable to create new access keys. Our engineering team is actively working on mitigation and evaluating additional protective measures to restore normal service. We will continue to provide updates as progress is made.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 03:52 PM UTC
- Resolved
- Aug 01, 2026, 12:45 AM UTC
- Duration
- 8h 52m
Affected: CoreWeave InferenceCoreWeave Networking (US-ORD1)CoreWeave Networking (US-LAS1)CoreWeave Networking (US-LGA1)CoreWeave Networking (US-EAST-12A)CoreWeave Networking (US-WEST-01)CoreWeave Networking (RDU1)CoreWeave Cloud Console (GLOBAL)
Timeline · 2 updates
-
identified Jul 31, 2026, 03:52 PM UTC
Hello, We are actively investigating elevated error rates affecting requests to some models available through CoreWeave Serverless and W&B Inference. Customers may experience failed requests. 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 the inconvenience and appreciate your patience. Thank You, CoreWeave Support
-
monitoring Jul 31, 2026, 05:01 PM UTC
Hello, The issue affecting some models available through CoreWeave Serverless and W&B Inference has been mitigated. Service has recovered, and we are monitoring performance to ensure continued stability. We will provide another update when monitoring is complete. We apologize for the inconvenience and appreciate your patience. Thank You, CoreWeave Support
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 01:57 AM UTC
- Resolved
- Jul 29, 2026, 06:50 AM UTC
- Duration
- 4h 52m
Affected: CoreWeave Object StorageCoreWeave Networking (US-EAST-06)
Timeline · 3 updates
-
investigating Jul 29, 2026, 01:57 AM UTC
We are currently investigating an elevated rate of failed requests to CoreWeave AI Object Storage in the US-EAST-06 region.
-
identified Jul 29, 2026, 01:58 AM UTC
We have identified the issue and are continuing to work on a resolution at this time.
-
monitoring Jul 29, 2026, 05:34 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 →
- Detected by Pingoru
- Jul 21, 2026, 10:03 PM UTC
- Resolved
- Jul 21, 2026, 10:55 PM UTC
- Duration
- 51m
Affected: CoreWeave ServicesCoreWeave Networking (CA-EAST-01)CoreWeave Networking (US-EAST-01)CoreWeave Networking (US-EAST-02)CoreWeave Networking (US-EAST-03)CoreWeave Networking (US-EAST-04)CoreWeave Networking (US-EAST-06)CoreWeave Networking (US-EAST-08)CoreWeave Networking (US-EAST-11)CoreWeave Networking (US-EAST-12A)CoreWeave Networking (US-EAST-13)CoreWeave Networking (US-EAST-14)CoreWeave Networking (US-EAST-14)CoreWeave Networking (US-EAST-15)
Timeline · 2 updates
-
investigating Jul 21, 2026, 10:03 PM UTC
We're currently investigating an issue that is preventing metrics and dashboards from loading for resources in our US-EAST regions. Customers may be unable to view cluster and node metrics in Grafana, and monitoring queries for US-EAST resources are returning errors. This is limited to metrics visibility only - It does not affect the health, availability, or performance of your running workloads, clusters, or nodes - compute continues to operate normally. Other regions (US-WEST and US-CENTRAL) are unaffected and their dashboards remain fully available. Our engineers are actively investigating and working to restore metrics access as quickly as possible. We apologize for the disruption and appreciate your patience.
-
monitoring Jul 21, 2026, 10:38 PM UTC
Metrics and dashboards for our US-EAST region have been restored, and monitoring queries are returning results normally again. Our engineers have applied a fix and are continuing to monitor closely to confirm full stability. As noted earlier, this issue was limited to metrics visibility and did not affect the health, availability, or performance of running workloads, clusters, or nodes. If you're still seeing gaps or errors when loading US-EAST metrics, please let us know. We'll post a final update once we've confirmed the region is fully stable. Thank you for your patience during the disruption.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 08:30 PM UTC
- Resolved
- Jul 21, 2026, 09:06 PM UTC
- Duration
- 36m
Affected: CoreWeave ServicesCoreWeave LoggingCoreWeave Networking (EU-NORTH-04)CoreWeave Networking (EU-NORTH-05)
Timeline · 2 updates
-
investigating Jul 21, 2026, 08:30 PM UTC
Hello , We're investigating an issue affecting metrics and logs in EU-NORTH. Customers with workloads in EU-NORTH-04 and EU-NORTH-05 may see missing metrics and logs. Compute and running workloads are not affected. Our team is actively working on to remediate the issue. We will keep you posted as we progress. We apologise for any inconvenienve and thank you for your patience! Thanks, CoreWeave Support
-
monitoring Jul 21, 2026, 08:41 PM UTC
A fix has been applied and connectivity for the EU-NORTH region has been restored. Metrics and logs for workloads in EU-NORTH-04 and EU-NORTH-05 are catching up, and we are monitoring to confirm full recovery. Compute and running workloads were not affected. We will confirm once the issue is fully resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 04:04 PM UTC
- Resolved
- Jul 16, 2026, 10:47 AM UTC
- Duration
- 18h 43m
Affected: CoreWeave CloudCoreWeave InfrastructureCoreWeave Premium Shared Filesystem VolumesCoreWeave Object StorageCoreWeave ServicesCoreWeave LoggingCoreWeave InferenceCoreWeave Shared Filesystem VolumesCoreWeave Block Storage VolumesCoreweave NetworkCoreWeave BareMetalCoreWeave NetworkingCoreWeave Networking (US-ORD1)CoreWeave Networking (US-LAS1)CoreWeave Networking (US-LGA1)CoreWeave Networking (US-RNO2)CoreWeave Networking (CA-EAST-01)CoreWeave Networking (US-CENTRAL-01)CoreWeave Networking (US-CENTRAL-02)CoreWeave Networking (US-CENTRAL-06)CoreWeave Networking (US-CENTRAL-07)CoreWeave Networking (US-CENTRAL-08)CoreWeave Networking (US-CENTRAL-10A)CoreWeave Networking (US-EAST-01)CoreWeave Networking (US-EAST-02)CoreWeave Networking (US-EAST-03)CoreWeave Networking (US-EAST-04)CoreWeave Networking (US-EAST-06)CoreWeave Networking (US-EAST-08)CoreWeave Networking (US-EAST-11)CoreWeave Networking (US-EAST-12A)CoreWeave Networking (US-EAST-13)CoreWeave Networking (US-EAST-14)CoreWeave Networking (US-EAST-14)CoreWeave Networking (US-WEST-01)CoreWeave Networking (US-WEST-02)CoreWeave Networking (US-WEST-03)CoreWeave Networking (US-WEST-04)CoreWeave Networking (US-WEST-07)CoreWeave Networking (US-WEST-09)CoreWeave Networking (US-WEST-10)CoreWeave Networking (EU-SOUTH-03)CoreWeave Networking (EU-SOUTH-04)CoreWeave Networking (EU-NORTH-02)CoreWeave Networking (US-LAB-01)CoreWeave Networking (NORTH AMERICA)CoreWeave Networking (GLOBAL)CoreWeave Networking (RDU1)CoreWeave Networking (US-CENTRAL-09A)CoreWeave Networking (EU-NORTH-04)CoreWeave Networking (EU-NORTH-05)CoreWeave Networking (US-CENTRAL-05)CoreWeave Networking (US-CENTRAL-11)CoreWeave Networking (US-EAST-15)
Timeline · 3 updates
-
investigating Jul 15, 2026, 04:04 PM UTC
Hello, We are actively investigating an issue impacting CW Services Globally including Console. 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
-
identified Jul 15, 2026, 04:50 PM UTC
We have identified the issue as a disruption to CW managed authentication. While actual health of cluster(s) are fine, anyone using CW managed authentication will be unable to authenticate due to an outage in our authentication service. While the authentication service is down, if you are able to bypass your CW managed Authentication, you will still be able to access your cluster(s). We are urgently working on a fix to our authentication service in parallel and will continue to post updates to this status page.
-
monitoring Jul 15, 2026, 05:52 PM UTC
We believe this incident has been mitigated. A fix went out to our authentication service and we're seeing a return to cluster/console access . We are continuing to monitor to ensure stability. If you continue to experience any issues, please reach out to support: [email protected]
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 03:27 AM UTC
- Resolved
- Jul 11, 2026, 05:21 AM UTC
- Duration
- 1h 54m
Affected: CoreWeave Object StorageCoreWeave Networking (GLOBAL)
Timeline · 3 updates
-
investigating Jul 11, 2026, 03:27 AM UTC
Hello, We are actively investigating an issue that may be impacting our object storage services, including the ability to create new access credentials. 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
-
identified Jul 11, 2026, 04:34 AM UTC
We have identified an issue affecting the creation of new access keys and temporary credentials for CoreWeave AI Object Storage. Existing credentials and stored data are unaffected. Our engineers are applying a fix and will post another update shortly.
-
monitoring Jul 11, 2026, 04:52 AM UTC
We have applied a fix, and creating new access keys and temporary credentials for CoreWeave AI Object Storage is working normally again. We are monitoring to confirm stability.
Read the full incident report →
- Detected by Pingoru
- Jul 11, 2026, 02:41 AM UTC
- Resolved
- Jul 11, 2026, 03:52 AM UTC
- Duration
- 1h 11m
Affected: CoreWeave InferenceCoreWeave Networking (US-ORD1)CoreWeave Networking (US-LAS1)CoreWeave Networking (US-LGA1)CoreWeave Networking (US-EAST-12A)CoreWeave Networking (US-WEST-01)CoreWeave Networking (RDU1)
Timeline · 3 updates
-
investigating Jul 11, 2026, 02:41 AM UTC
We are investigating reports of failing requests to CoreWeave Inference services. 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
-
identified Jul 11, 2026, 02:49 AM UTC
We have identified the root cause of the issue and are actively working on resolving it at this time.
-
monitoring Jul 11, 2026, 03:30 AM UTC
We believe the issue is resolved, and our services are now operational. If you are continuing to experience issues, please reach out to [email protected].
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 10:17 PM UTC
- Resolved
- Jul 07, 2026, 11:51 PM UTC
- Duration
- 1h 33m
Affected: CoreWeave InfrastructureCoreWeave Networking (GLOBAL)
Timeline · 3 updates
-
investigating Jul 07, 2026, 10:17 PM UTC
We are investigating reports of node delivery/reboot failures occurring in all regions. 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
-
identified Jul 07, 2026, 10:29 PM UTC
The root cause has been identified and we are working on a resolution at this time.
-
monitoring Jul 07, 2026, 11:09 PM UTC
This incident has been mitigated. Node delivery and node reboot operations have returned to normal in all regions. We are continuing to monitor to ensure stability. If you continue to experience any issues, please reach out to support: [email protected] We apologize for the disruption this caused and thank you for your patience while we worked to resolve the matter. Thank you, CoreWeave Support
Read the full incident report →
- 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
-
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
-
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 →
- 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
-
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 →
- 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
-
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.
-
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.
-
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 →
- Detected by Pingoru
- Jun 04, 2026, 06:34 PM UTC
- Resolved
- Jun 05, 2026, 03:27 AM UTC
- Duration
- 8h 53m
Affected: CoreWeave Premium Shared Filesystem VolumesCoreWeave Object StorageCoreweave Network (US-EAST-04)
Timeline · 9 updates
Read the full incident report →
- 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
-
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.
-
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 →
- 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
-
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
-
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.
-
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.
-
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 →
- 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
-
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 →
- 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
-
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
-
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
-
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 →
- 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
-
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
-
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 →
- 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
-
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 →
- 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
-
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
-
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 →
- 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
-
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.
-
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 →
