Chroma

Affected: 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 low confidence (taxonomy v0.2).

1. investigating 2026-08-18 16:52 UTC

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

2. monitoring 2026-08-18 18:25 UTC

   We implemented a fix and are currently monitoring the result.

3. resolved 2026-08-18 19:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: 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. investigating 2026-06-29 21:32 UTC

   We are currently investigating a degradation in our indexing throughput affecting a small precentage of active collections due to a new release

2. identified 2026-06-29 21:45 UTC

   We have identified the root cause and are rolling out a fix

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

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Hosted embedding service

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: AWS.

1. identified 2026-05-08 01:04 UTC

   Our infrastructure is affected by an outage in AWS: We are monitoring the incident and working to restore service.

2. resolved 2026-05-08 02:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: 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-03-13 02:17 UTC

   We are currently investigating an incident where some collections are experiencing internal server errors when queried.

2. identified 2026-03-13 02:53 UTC

   We have identified the issue and are working on a fix.

3. resolved 2026-03-13 04:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: 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-27 23:57 UTC

   We are currently investigating this incident where Chroma Cloud is returning 504 errors at an increased rate and query latencies are degraded.

2. investigating 2026-01-28 00:25 UTC

   We implemented a fix and are currently monitoring the system as health restores.

3. resolved 2026-01-28 01:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard, 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).

Names an upstream provider: AWS.

1. investigating 2025-11-01 20:39 UTC

   We are experiencing a large surge in traffic and queries are degraded for collections with recently added data. We are currently scaling out the cluster in order to accommodate more traffic

2. identified 2025-11-01 20:43 UTC

   We are continuing to work on a fix for this incident. Performance is stabilizing

3. resolved 2025-11-01 21:02 UTC

   Cluster is confirmed as stable and latencies have returned to normal

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: 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 2025-10-03 13:30 UTC

   We are currently investigating this incident.

2. resolved 2025-10-03 14:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Package Search MCP

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 2025-09-21 03:48 UTC

   We are currently investigating this incident.

2. resolved 2025-09-21 04:44 UTC

   We've identified and fixed it

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard, API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-20 20:13 UTC

   We are currently investigating this incident.

2. resolved 2025-08-20 20:27 UTC

   This incident has been resolved. A faulty change was rolled out to our authentication system, the implicated change has been rolled back.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard

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 2025-08-06 16:12 UTC

   Our billing data pipeline is currently processing events slower than targeted. Billing data may be slightly behing.

2. resolved 2025-08-06 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard, 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 2025-06-24 18:44 UTC

   We are currently investigating this incident.

2. monitoring 2025-06-24 18:50 UTC

   Engineers have identified the problem and have fully mitigated the issue. We will continue to monitor the situation.

3. resolved 2025-06-24 19:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard, API

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).

Names an upstream provider: AWS.

1. investigating 2025-05-30 02:56 UTC

   We are currently investigating degradation to all DML operations on Chroma Cloud us-east-1\\. DDLs remain healthy.

2. monitoring 2025-05-30 03:34 UTC

   We have reverted the offending configuration change, which routed traffic to a proxy service that was failing. This issue is now resolved.

3. resolved 2025-05-30 03:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: API

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 2025-05-06 21:42 UTC

   On 5/6 at 2:24 PST we observed a slow down in indexing speed. We are scaling our cluster to accommodate increased load.

2. resolved 2025-05-06 22:44 UTC

   This issue is resolved

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: Dashboard

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 2025-04-18 23:00 UTC

   We are receiving reports of an error while creating a new account. Existing users are not affected.

2. resolved 2025-04-21 17:00 UTC

   This incident has been resolved. The error was not detected by our alerting systems, and led to a prolonged outage. We are updating our alerting systems to detect persistent issues like this in the future for a faster response.

Excerpts are shortened. Read the full incident on Chroma's status page.

Affected: 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 2025-04-15 15:00 UTC

   We are currently investigating elevated API latencies to core Chroma APIs.

2. identified 2025-04-15 15:45 UTC

   We have identified the root cause of the issue and are resolving.

3. resolved 2025-04-15 16:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Chroma's status page.