Zep

Affected: API, Web App, Episode Processing

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-10-16 15:25 UTC

   We are currently investigating this issue.

2. monitoring 2026-10-16 15:44 UTC

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

3. resolved 2026-10-16 18:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-09-15 15:57 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-15 17:09 UTC

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

3. resolved 2026-09-15 19:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-09-10 15:45 UTC

   We are currently investigating this issue.

2. identified 2026-09-10 16:14 UTC

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

3. monitoring 2026-09-10 16:30 UTC

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

4. resolved 2026-09-10 18:11 UTC

   This incident has been resolved.

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

Affected: API, Episode Processing

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. investigating 2026-09-03 21:48 UTC

   We are currently investigating this issue.

2. investigating 2026-09-03 21:49 UTC

   We are continuing to investigate this issue.

3. identified 2026-09-03 22:12 UTC

   We are impacted by an outage in AWS us-west-2 impacting multiple services. We've seen some recovery in latency, but continue to see errors and do not believe the outage is resolved on AWS' side. We will provide an update in the next 30-60 minutes as we learn more.

4. monitoring 2026-09-03 22:38 UTC

   AWS has begun to see some recovery, and we've seen that take effect within our own services. We will continue to monitor for errors and increased latency for the next 60 minutes.

5. resolved 2026-09-03 23:44 UTC

   We've continued to see healthy outcomes for our services, both in error rates and latencies, and consider this incident resolved after an hour of monitoring.

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

Affected: API, Episode Processing

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-08-27 19:39 UTC

   We are investigating an issue that is impacting retrieval and episode processing.

2. monitoring 2026-08-27 20:10 UTC

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

3. resolved 2026-08-27 22:02 UTC

   This incident has been resolved.

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

Affected: API, Web App

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-06-09 16:36 UTC

   We are currently investigating this issue.

2. investigating 2026-06-09 16:37 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-09 17:08 UTC

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

4. resolved 2026-06-09 19:49 UTC

   This incident has been resolved.

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

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. resolved 2026-05-28 20:30 UTC

   We are currently investigating this issue.

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

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. resolved 2026-04-22 11:00 UTC

   Some customers may be experienced elevated API error rates. We have resolved the issue and are continuing to monitor the Zep service.

Excerpts are shortened. Read the full incident on Zep'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-04-08 16:16 UTC

   We are currently investigating this issue.

2. resolved 2026-04-09 01:25 UTC

   Resolved and monitoring.

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

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. resolved 2026-03-31 18:00 UTC

   Elevated API error rates for some operations occurred over a 3 minute period. We've identified the issue and resolved it. We continue to monitor the service for stability.

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

Affected: API, Web App

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

   We are currently investigating this issue.

2. monitoring 2026-03-23 21:45 UTC

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

3. resolved 2026-03-24 03:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-03-23 02:41 UTC

   We're investigating elevated API error rates.

2. investigating 2026-03-23 03:00 UTC

   We have identified the issue and implementing mitigations.

3. monitoring 2026-03-23 03:00 UTC

   Mitigated. We're monitoring.

4. resolved 2026-03-23 03:40 UTC

   Service is nominal. We're closing this issue.

Excerpts are shortened. Read the full incident on Zep'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-02-25 21:52 UTC

   We are currently investigating this issue.

2. resolved 2026-02-25 22:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-02-16 16:52 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-16 17:22 UTC

   A fix has been deployed and error rates have dropped to nominal. We'll continue monitoring the service for the next while.

3. resolved 2026-02-16 17:27 UTC

   This incident has been resolved.

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

Affected: API, Web App

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-10 17:51 UTC

   We are currently investigating this issue.

2. resolved 2026-02-10 18:30 UTC

   This incident has been resolved.

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

Affected: Web App

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-09 22:08 UTC

   We are currently investigating this issue.

2. identified 2026-02-09 22:09 UTC

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

3. resolved 2026-02-09 22:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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. identified 2026-02-04 06:36 UTC

   We're experiencing elevated API error rates. We've identified the cause and are working to resolve the issue.

2. monitoring 2026-02-04 06:40 UTC

   We've resolved the infrastructure issue and are monitoring as the service returns to normal.

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

   This issue is resolved.

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

Affected: Episode Processing

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-02 15:22 UTC

   Some customers may be experiencing delayed episode ingestion. We’ve identified the issue and are working on a fix.

2. monitoring 2026-02-02 15:55 UTC

   The issue has been fixed. Queues are draining and they may take an hour or two to clear. We're continuing to monitor.

3. resolved 2026-02-02 19:31 UTC

   We've caught up on ingestion queues. This issue has been resolved.

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

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. resolved 2026-01-29 03:30 UTC

   UPDATE: This incident has been resolved. Zep context retrieval is currently impacted by an outage at our upstream search provider. We are in contact with the provider and they're rolling out a fix to address the outage.

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

Affected: API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-17 17:32 UTC

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

2. resolved 2025-12-17 17:47 UTC

   This incident has been resolved.

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

Affected: API

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 medium confidence (taxonomy v0.2).

1. investigating 2025-12-15 15:47 UTC

   We're currently experiencing sporadic latency spikes on our retrieval endpoints. We're working with an upstream provider to mitigate this issue.

2. resolved 2025-12-15 18:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-30 17:55 UTC

   We are currently investigating this issue.

2. resolved 2025-10-30 18:05 UTC

   This incident has been resolved.

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

Affected: Web App

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 2025-10-08 21:40 UTC

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

2. identified 2025-10-08 21:47 UTC

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

3. resolved 2025-10-08 21:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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. identified 2025-10-02 15:24 UTC

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

2. resolved 2025-10-02 16:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-09-16 01:55 UTC

   We are currently investigating this issue.

2. resolved 2025-09-16 02:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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. identified 2025-09-10 17:17 UTC

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

2. resolved 2025-09-10 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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. identified 2025-09-02 18:23 UTC

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

2. resolved 2025-09-02 18:53 UTC

   This incident has been resolved.

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

Affected: API

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-27 23:28 UTC

   We are currently investigating this issue.

2. investigating 2025-08-27 23:44 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-08-28 00:52 UTC

   During a graph database migration to improve search latency, nodes in cluster ran out of file descriptors. We quickly identified the issue and implemented a fix. Nodes took some time to recover and rejoin the cluster. We will be running a post-mortem to understand and address...

4. monitoring 2025-08-28 00:53 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-08-28 01:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-08-27 20:11 UTC

   We are currently investigating this issue.

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

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Zep'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-08-17 20:56 UTC

   We experienced high error rates on our retrieval endpoints. We have identified the issue and fixed it

2. resolved 2025-08-17 20:57 UTC

   This incident has been resolved.

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

Affected: API

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-08-05 21:13 UTC

   We experienced a temporary disruption to our memory service due to a database schema migration. Customers may have encountered errors when adding messages and graph data to Zep. The issue has been resolved and all data sent to Zep has been processed successfully.

Excerpts are shortened. Read the full incident on Zep'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. monitoring 2025-08-01 18:52 UTC

   We have resolved the underlying issue, monitoring.

2. monitoring 2025-08-01 19:45 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-08-01 19:57 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Zep'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 2024-04-04 16:01 UTC

   We are currently investigating this issue.

2. investigating 2024-04-04 16:02 UTC

   We are continuing to investigate this issue.

3. monitoring 2024-04-04 16:05 UTC

   We believe we have fixed the issue, monitoring.

4. resolved 2024-04-04 17:27 UTC

   This incident has been resolved.

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

Affected: API, Web App

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 2024-03-26 17:47 UTC

   We are currently investigating.

2. investigating 2024-03-26 19:46 UTC

   We are continuing to investigate this issue.

3. resolved 2024-03-26 19:47 UTC

   We've identified and resolved the issue.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-07 15:30 UTC

   Our cross-cloud access to inference services impacted FactExtraction and Summarization, with fact tables and summaries not being created for new messages added to the service.

2. postmortem 2024-03-07 22:08 UTC

   We had a failure of our cross-cloud VPN infrastructure. Additional monitoring and other remediation has been put in place.

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