Weights & Biases (CoreWeave)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. resolved 2026-09-01 14:40 UTC

   An incident with Google Cloud caused our API and site to become degraded or unavailable. We apologize for the disruption. https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-15 22:35 UTC

   We are currently experiencing elevated errors fetching media files in Weights & Biases.

2. resolved 2026-07-16 00:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-15 06:46 UTC

   We are currently experiencing elevated ingestion delay due to high volume.

2. identified 2026-07-15 06:48 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-07-15 06:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-13 06:04 UTC

   We are experiencing metric ingestion delay of ~1 hour

2. resolved 2026-07-13 19:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-12 04:38 UTC

   We're currently experiencing elevated ingestion time of about 30 minutes for some run metrics.

2. resolved 2026-07-12 17:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Inference Endpoint

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-11 03:11 UTC

   Serverless Inference users could experience timeouts and 503 response codes while attempting to leverage models on the product. We are actively engaged in troubleshooting and will post an update here as soon as we know more.

2. monitoring 2026-07-11 03:36 UTC

   Impact has been mitigated.

3. resolved 2026-07-11 03:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-11 02:11 UTC

   We are currently seeing a backup in metric ingestion of up to 20 minutes

2. resolved 2026-07-11 03:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Auth0 User Authentication

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-26 07:13 UTC

   We are investigating an issue where logging in to wandb.ai may fail for some users.

2. identified 2026-06-26 07:18 UTC

   We have identified an issue with Auth0 that may cause some users to be unable to log in.

3. monitoring 2026-06-26 07:28 UTC

   An Auth0 incident that had earlier prevented logins has recovered, allowing restored login access. We are continuing to monitor the situation. Auth0 Incident: https://status.auth0.com/incidents/z8sc9m1gzqb7

4. resolved 2026-06-29 18:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-14 07:37 UTC

   We're investigating reports of the W&B web app (app.wandb.ai) showing a blank page on load for some users. The API and SDK data logging remain operational. A fix is in progress and we'll share an update soon.

2. investigating 2026-06-14 07:37 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-14 09:30 UTC

   A fix has been deployed and we are monitoring.

4. resolved 2026-06-14 20:59 UTC

   Web app has been restored.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-09 23:47 UTC

   We are currently responding to delay of up to 5 hours for metrics written into wandb. We have identified the issue and are working to process metrics as quickly as possible. There is no data loss and all data will be complete once the backlog has drained. We're very sorry for...

2. monitoring 2026-06-10 05:44 UTC

   We identified an infrastructure issue as the root cause and have resolved it. We are rapidly working through the backlog of ingested metrics and should fully catch up soon.

3. resolved 2026-06-10 07:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-09 09:32 UTC

   We are currently investigating an issue where metric ingestion is delayed for some runs up to 1 hour.

2. resolved 2026-06-09 09:55 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-26 19:47 UTC

   Starting at 10:48AM PST we experienced an incident causing missing metrics and slowness across the application. As of 12:10 PM metrics should now be restored (there was no data loss) and we are continuing to monitor performance.

2. resolved 2026-05-27 02:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-15 13:51 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. resolved 2026-05-15 16:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-10 13:19 UTC

   We identified an issue where updates to W&B Models runs may be delayed for up to 30 minutes. There is no data loss.

2. monitoring 2026-05-10 14:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-10 18:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-04 15:50 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-04 17:57 UTC

   The frontend and backend APIs have fully recovered after we mitigated excess load on the system. We will continue to actively monitor the situation to ensure stability.

3. investigating 2026-05-04 22:42 UTC

   We are currently investigating this issue.

4. monitoring 2026-05-05 00:31 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2026-05-05 00:36 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-05-05 04:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-29 15:51 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. resolved 2026-05-01 16:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 22:41 UTC

   We are currently investigating an issue where API requests may sporadically fail.

2. resolved 2026-04-29 02:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-22 06:00 UTC

   We are currently investigating an issue where requests are failing.

2. monitoring 2026-04-22 07:35 UTC

   The issue has been identified and a fix has been rolled out. We are monitoring for any further issues.

3. monitoring 2026-04-22 15:30 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-04-28 04:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-06 15:26 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-04-06 16:51 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-04-06 17:12 UTC

   We are seeing the site recover and be fully operational - we are continuing to actively monitor the situation to ensure stability.

4. resolved 2026-04-07 04:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-02 02:15 UTC

   We have identified a delay in files and media getting uploaded.

2. identified 2026-04-02 02:15 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2026-04-02 03:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Inference Endpoint

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-31 16:52 UTC

   The W&B Inference endpoint is currently unavailable. This is due to some maintenance on the gateway that was scheduled but that we missed the announcement step for. We expect intermittent outages between 9am and 11am PDT. We apologize for any inconvenience.

2. resolved 2026-03-31 18:12 UTC

   Maintenance has completed.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-20 20:55 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-20 20:55 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-20 21:13 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-11 17:50 UTC

   We are aware of an issue causing elevated API request latencies, resulting in degraded performance in the UI and SDK. Recent changes in traffic patterns are resulting in increased load, which we urgently are working to address.

2. monitoring 2026-03-11 23:58 UTC

   We've deployed mitigations and are actively monitoring. Request latencies have decreased but are not yet back to baseline. We appreciate your patience as we work to resolve this issue.

3. resolved 2026-03-12 23:33 UTC

   We've been monitoring request latencies over the past 24 hours and they are back within our normal ranges.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-07 20:28 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. resolved 2026-03-13 15:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-07 04:16 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-07 04:16 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-07 04:21 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-07 01:05 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-07 01:05 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-07 01:06 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-06 22:43 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-06 22:43 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-06 22:44 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-05 23:48 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-05 23:48 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-05 23:50 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-05 19:03 UTC

   We're experiencing an elevated level of latency across the site and API. We are actively investigating the issue.

2. investigating 2026-03-05 19:07 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-05 20:02 UTC

   We have implemented a set of mitigations - site performance is significantly improved and we are investigating further fixes.

4. monitoring 2026-03-05 21:36 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2026-03-06 00:19 UTC

   UI & API latency has returned to normal ranges

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-05 13:35 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-05 13:35 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-05 13:43 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-05 01:11 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-05 01:12 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-03-05 01:12 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-04 10:00 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2026-03-04 10:01 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-01 03:22 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-01 03:27 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. investigating 2026-03-01 03:27 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

4. investigating 2026-03-01 03:31 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

5. investigating 2026-03-01 03:32 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

6. resolved 2026-03-01 03:39 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-01 03:05 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved 2026-03-01 03:08 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-01 02:42 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-03-01 02:47 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. investigating 2026-03-01 02:47 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

4. resolved 2026-03-01 02:50 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-28 00:55 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. resolved 2026-03-01 02:31 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-24 22:10 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. resolved 2026-02-26 19:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 21:42 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-24 21:42 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-24 22:07 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-02-24 21:00 UTC

   We're aware of an issue causing elevated error rates for certain projects due to a database misconfiguration. We have applied a fix and are actively monitoring.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Metrics Ingestion Pipeline

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-21 22:45 UTC

   We are currently experiencing delays in processing newly logged metrics. As a result, recent metrics from active runs may take longer than usual to appear in charts, dashboards, reports, and API queries. No data is lost. All metrics are being processed and will become visible...

2. identified 2026-02-22 05:17 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-22 05:18 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-21 07:09 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-21 07:09 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-21 07:11 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-19 23:45 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-19 23:45 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-19 23:49 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-16 21:39 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-16 21:40 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-16 21:40 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-16 16:52 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-16 16:52 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-16 16:53 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-15 12:18 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-15 12:19 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-15 12:22 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-15 11:19 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-02-15 11:20 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-02-15 11:22 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-09 21:41 UTC

   A recent deployment caused an issue affecting read access to some projects with active runs. We're actively working on fixing the issue.

2. resolved 2026-02-10 00:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-21 16:09 UTC

   We are currently investigating elevated latency across the application since 7:08am PST.

2. monitoring 2026-01-21 16:45 UTC

   Issue appears resolved as of 8:18am. We are continuing to monitor.

3. resolved 2026-01-21 22:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-21 15:19 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. investigating 2026-01-21 15:19 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

3. resolved 2026-01-21 15:21 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.

Affected: Backend API, Frontend

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-15 04:48 UTC

   We are aware of ingestion delay for some projects and working to resolve it.

2. identified 2026-01-15 07:13 UTC

   We have implemented a mitigation and are making progress against the backlog.

3. resolved 2026-01-15 18:26 UTC

   Our systems have fully caught up with the backlog. The API should correctly return up-to-date metrics for experiments in all projects. We sincerely appreciate your patience as we worked to resolve the issue.

Excerpts are shortened. Read the full incident on Weights & Biases (CoreWeave)'s status page.