Zep Software had 25 outages in the last 2 years totaling 40h 16m of downtime — averaging 1 incident per month.
There were 25 Zep Software outages since August 1, 2025 totaling 40h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
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.
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.
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.
testing, please ignore
We are investigating an issue that is impacting retrieval and episode processing.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Some customers may be experienced elevated API error rates. We have resolved the issue and are continuing to monitor the Zep service.
We are currently investigating this issue.
Resolved and monitoring.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating elevated API error rates.
We have identified the issue and implementing mitigations.
Mitigated. We're monitoring.
Service is nominal. We're closing this issue.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been deployed and error rates have dropped to nominal. We'll continue monitoring the service for the next while.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Some customers may be experiencing delayed episode ingestion. We’ve identified the issue and are working on a fix.
The issue has been fixed. Queues are draining and they may take an hour or two to clear. We're continuing to monitor.
We've caught up on ingestion queues. This issue has been resolved.
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.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're currently experiencing sporadic latency spikes on our retrieval endpoints. We're working with an upstream provider to mitigate this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
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.