- Detected by Pingoru
- Sep 15, 2026, 11:38 PM UTC
- Resolved
- Sep 16, 2026, 02:57 AM UTC
- Duration
- 3h 18m
Affected: CoreWeave InferenceCoreWeave Cloud Console (GLOBAL)
Timeline · 3 updates
-
investigating Sep 15, 2026, 11:38 PM UTC
We are investigating an issue that is causing errors when creating new Dedicated Inference deployments or editing existing ones. Deployments that are already running are not affected and continue to serve traffic normally.
-
identified Sep 15, 2026, 11:42 PM UTC
We have identified the cause of the errors affecting Dedicated Inference deployment creates and edits, and a fix is being prepared. Running deployments remain unaffected and are serving traffic normally.
-
monitoring Sep 16, 2026, 01:36 AM UTC
A fix has been applied and Dedicated Inference deployment creates and edits are succeeding again. We are monitoring to confirm full recovery. If you are still seeing errors, please reach out to our support team.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2026, 10:12 AM UTC
- Resolved
- Sep 11, 2026, 11:14 AM UTC
- Duration
- 1h 2m
Affected: CoreWeave Object StorageCoreWeave Cloud Console (GLOBAL)
Timeline · 3 updates
-
investigating Sep 11, 2026, 10:12 AM UTC
Hello, We are currently investigating an issue affecting CoreWeave Cloud authentication (OIDC) services. Customers may experience issues accessing CAIOS, authenticating through OIDC, or obtaining credentials for CAIOS workloads. Our team is actively working with the highest priority level to restore full functionality as quickly as possible. We apologise for any inconvenience and appreciate your patience while we work to resolve the issue. — CoreWeave Support
-
investigating Sep 11, 2026, 10:29 AM UTC
Hello, We are currently investigating an issue affecting CoreWeave Cloud authentication (OIDC) services. Customers may experience issues accessing CoreWeave AI Object Storage (CAIOS), authenticating through OIDC, or obtaining credentials for CAIOS workloads. Our team is actively working with the highest priority level to restore full functionality as quickly as possible. We apologise for any inconvenience and appreciate your patience while we work to resolve the issue. — CoreWeave Support
-
monitoring Sep 11, 2026, 10:43 AM UTC
Hello, The issue has been mitigated. CoreWeave Cloud authentication (OIDC) access to CoreWeave AI Object Storage (CAIOS) has returned to baseline, and affected workloads should now operate normally. Our teams continue to monitor this to prevent any recurrence. Thank you for your patience during this window. Thank You, CoreWeave Support Team.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 08:02 PM UTC
- Resolved
- Sep 03, 2026, 11:26 PM UTC
- Duration
- 3h 23m
Affected: Coreweave NetworkCoreWeave Networking (US-CENTRAL-08A)
Timeline · 2 updates
-
identified Sep 03, 2026, 08:02 PM UTC
Hello, We are investigating degraded performance on the backend GPU interconnect fabric in US-CENTRAL-08A. Multi-node GPU workloads may see reduced bandwidth or increased latency. Our engineering team is actively working on this. We will provide updates as the situation develops. If you have any questions, please reach out to our support team at [email protected] or raise an inquiry in your dedicated Slack channel. Thank You, CoreWeave Support
-
identified Sep 03, 2026, 09:48 PM UTC
Hello, We have identified the issue affecting the backend GPU interconnect in US-CENTRAL-08A and mitigation is in progress. Multi-node GPU workloads may still see reduced bandwidth or increased latency while we complete this work. We will update you as the situation develops. We appreciate your patience as we work through this. Thank You, CoreWeave Support
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 02:05 AM UTC
- Resolved
- Sep 02, 2026, 11:42 PM UTC
- Duration
- 21h 36m
Affected: CoreWeave LoggingCoreWeave 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)CoreWeave Networking (US-EAST-18A)
Timeline · 2 updates
-
investigating Sep 02, 2026, 02:05 AM UTC
We're investigating degraded performance with metrics in US-EAST. Querying US-EAST metrics in Grafana may be slow or return intermittent errors. Metric ingestion is degraded, but no metric data is being lost, and customer workloads are not affected. We'll provide updates as we remediate.
-
identified Sep 02, 2026, 07:00 AM UTC
We have identified the cause of the metrics degradation and are actively working on a fix. We have also taken steps to stabilize the metrics query endpoints, and we continue to monitor overall system health. We will share further updates as remediation progresses.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2026, 06:52 PM UTC
- Resolved
- Aug 28, 2026, 09:12 PM UTC
- Duration
- 2h 19m
Affected: CoreWeave Premium Shared Filesystem VolumesCoreWeave Networking (US-EAST-13)
Timeline · 3 updates
-
investigating Aug 28, 2026, 06:52 PM UTC
Hello, We are actively investigating an issue that is impacting our storage services in US-EAST-13A. 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 Aug 28, 2026, 07:28 PM UTC
We have identified the root cause of the issue and are actively working on remediating the cluster. We will update you when we have pushed a fix.
-
monitoring Aug 28, 2026, 07:38 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
- Aug 27, 2026, 03:37 AM UTC
- Resolved
- Aug 27, 2026, 08:56 PM UTC
- Duration
- 17h 19m
Affected: CoreWeave Object StorageCoreWeave Networking (US-WEST-01)
Timeline · 5 updates
-
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.
-
identified Aug 27, 2026, 09:03 AM UTC
We have identified the issue and are continuing to work on a resolution at this time.
-
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].
-
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.
-
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].
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 07:32 PM UTC
- Resolved
- Aug 26, 2026, 08:12 PM UTC
- Duration
- 39m
Affected: CoreWeave CloudCoreWeave Cloud ConsoleCoreWeave Cloud Console (GLOBAL)
Timeline · 1 update
-
identified Aug 26, 2026, 07:32 PM UTC
Hello, We have identified an issue affecting CoreWeave Cloud console services. Customers may experience issues creating, deleting, or updating CKS clusters from the console or Terraform. Our team has identified the issue and is actively working to restore full functionality as quickly as possible. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue. — CoreWeave Support
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 05:12 PM UTC
- Resolved
- Aug 20, 2026, 05:34 PM UTC
- Duration
- 22m
Affected: CoreWeave CloudCoreWeave InfrastructureCoreWeave Networking (US-CENTRAL-08A)
Timeline · 1 update
-
investigating Aug 20, 2026, 05:12 PM UTC
We are investigating a loss of production GPU capacity affecting a subset (19) of GB300 racks in DH204. Affected nodes have intermittently gone unhealthy and been evicted; a number have been taken out of production for recovery. Affected: GB300 compute, DH204 (clusters msl-cw-use2-1, msl-cw-use2-2) Current impact: Several racks are below the 16-node threshold for a full NVL64 domain, so multi-node jobs targeting those racks may fail to place or may be interrupted. Capacity in other datahalls and regions is unaffected. The first node losses were observed at approximately 2026-08-19 19:00 UTC. Fleet Operations has been recovering nodes by reboot since then, and additional engineering teams were engaged at 16:30 UTC today. We will keep you posted on further details as we progress. Thank you for your patience and cooperation while we are investigating.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 11:21 PM UTC
- Resolved
- Aug 14, 2026, 12:59 AM UTC
- Duration
- 1h 37m
Affected: CoreWeave CloudCoreWeave ServicesCoreweave NetworkCoreWeave NetworkingCoreWeave Networking (EU-SOUTH-03)
Timeline · 1 update
-
investigating Aug 13, 2026, 11:21 PM UTC
Beginning at 22:51 UTC on 13 August 2026, we identified a network connectivity issue affecting internal service communication within the EU-SOUTH-03B availability zone. Customers in this availability zone may experience intermittent errors or delays when performing cluster control-plane operations, such as Kubernetes API requests. Running workloads and compute nodes are not currently showing impact. Our networking teams are actively engaged and investigating. Other availability zones and regions are unaffected.
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 11:00 PM UTC
- Resolved
- Aug 11, 2026, 07:10 PM UTC
- Duration
- 20h 10m
Affected: CoreWeave Premium Shared Filesystem VolumesCoreWeave Networking (US-EAST-02)
Timeline · 2 updates
-
investigating Aug 10, 2026, 11:00 PM UTC
Hello, We are actively investigating a storage issue that may be impacting our storage services in US-EAST-02A. 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 Aug 10, 2026, 11:28 PM 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.
Read the full incident report →
- Detected by Pingoru
- Aug 09, 2026, 03:31 PM UTC
- Resolved
- Aug 09, 2026, 11:06 PM UTC
- Duration
- 7h 34m
Affected: CoreWeave InfrastructureCoreWeave Networking (US-RNO2)
Timeline · 3 updates
-
investigating Aug 09, 2026, 03:31 PM UTC
We are currently investigating an issue related to node delivery/reboot failures occurring in the RNO2 region. 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 Aug 09, 2026, 05:22 PM UTC
The root cause has been identified and we are working on a resolution at this time.
-
monitoring Aug 09, 2026, 05:41 PM UTC
This incident has been mitigated. Node delivery and node reboot operations have now returned to normal. 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
- Aug 04, 2026, 10:56 PM UTC
- Resolved
- Aug 05, 2026, 12:36 AM UTC
- Duration
- 1h 40m
Affected: CoreWeave InfrastructureCoreWeave NetworkingCoreWeave Networking (US-EAST-04)
Timeline · 3 updates
-
investigating Aug 04, 2026, 10:56 PM UTC
We are investigating a networking hardware issue in US-EAST-04A affecting connectivity for a subset of nodes. Out of an abundance of caution, impacted nodes have been temporarily removed from service while our engineers work to restore connectivity. Customers may see a small number of nodes become unavailable or unschedulable during this time.
-
identified Aug 04, 2026, 11:53 PM UTC
Our engineers have identified the issue and remediation is underway. We will provide another update within the next hour or sooner.
-
monitoring Aug 05, 2026, 12:25 AM UTC
The issue has been resolved and affected nodes have returned to service. We will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 07:59 PM UTC
- Resolved
- Aug 06, 2026, 08:41 PM UTC
- Duration
- 3d
Affected: CoreWeave InfrastructureCoreWeave Networking (US-EAST-04)
Timeline · 2 updates
-
investigating Aug 03, 2026, 07:59 PM UTC
We are investigating an infrastucture degradation in the US-EAST-04A 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.
-
identified Aug 04, 2026, 04:53 PM UTC
We have identified a power issue and are working to bring spare capacity back online.
Read the full incident report →
- 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 Bare MetalCoreWeave 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-08A)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
- 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 →