Zep Software Outage History

Zep Software is up right now

Zep Software had 18 outages in the last 2 years totaling 26h 31m of downtime — averaging 0.7 incidents per month.

There were 18 Zep Software outages since August 1, 2025 totaling 26h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.getzep.com

Major April 22, 2026

Elevated Error Rates

Detected by Pingoru
Apr 22, 2026, 02:47 PM UTC
Resolved
Apr 22, 2026, 11:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 22, 2026, 02:47 PM UTC

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

Read the full incident report →

Minor April 8, 2026

Elevated error rates on retrieval

Detected by Pingoru
Apr 08, 2026, 04:16 PM UTC
Resolved
Apr 09, 2026, 01:25 AM UTC
Duration
9h 9m
Affected: API
Timeline · 2 updates
  1. investigating Apr 08, 2026, 04:16 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 09, 2026, 01:25 AM UTC

    Resolved and monitoring.

Read the full incident report →

Notice March 31, 2026

Elevated API Error Rates

Detected by Pingoru
Mar 31, 2026, 06:34 PM UTC
Resolved
Mar 31, 2026, 06:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 31, 2026, 06:34 PM 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.

Read the full incident report →

Major March 23, 2026

Service outage

Detected by Pingoru
Mar 23, 2026, 09:27 PM UTC
Resolved
Mar 24, 2026, 03:45 AM UTC
Duration
6h 17m
Affected: APIWeb App
Timeline · 3 updates
  1. investigating Mar 23, 2026, 09:27 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 23, 2026, 09:45 PM UTC

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

  3. resolved Mar 24, 2026, 03:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 23, 2026

High API Error Rates

Detected by Pingoru
Mar 23, 2026, 02:41 AM UTC
Resolved
Mar 23, 2026, 03:40 AM UTC
Duration
59m
Affected: API
Timeline · 4 updates
  1. investigating Mar 23, 2026, 02:41 AM UTC

    We're investigating elevated API error rates.

  2. investigating Mar 23, 2026, 03:00 AM UTC

    We have identified the issue and implementing mitigations.

  3. monitoring Mar 23, 2026, 03:00 AM UTC

    Mitigated. We're monitoring.

  4. resolved Mar 23, 2026, 03:40 AM UTC

    Service is nominal. We're closing this issue.

Read the full incident report →

Major February 25, 2026

Elevated API error rate

Detected by Pingoru
Feb 25, 2026, 09:52 PM UTC
Resolved
Feb 25, 2026, 10:02 PM UTC
Duration
9m
Affected: API
Timeline · 2 updates
  1. investigating Feb 25, 2026, 09:52 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 25, 2026, 10:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 16, 2026

Elevated API errors

Detected by Pingoru
Feb 16, 2026, 04:52 PM UTC
Resolved
Feb 16, 2026, 05:27 PM UTC
Duration
34m
Affected: API
Timeline · 3 updates
  1. investigating Feb 16, 2026, 04:52 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 16, 2026, 05:22 PM 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 Feb 16, 2026, 05:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2026

Elevated latency and error rates

Detected by Pingoru
Feb 10, 2026, 05:51 PM UTC
Resolved
Feb 10, 2026, 06:30 PM UTC
Duration
38m
Affected: APIWeb App
Timeline · 2 updates
  1. investigating Feb 10, 2026, 05:51 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 10, 2026, 09:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 9, 2026

Webapp elevated error rate

Detected by Pingoru
Feb 09, 2026, 10:08 PM UTC
Resolved
Feb 09, 2026, 10:26 PM UTC
Duration
18m
Affected: Web App
Timeline · 3 updates
  1. investigating Feb 09, 2026, 10:08 PM UTC

    We are currently investigating this issue.

  2. identified Feb 09, 2026, 10:09 PM UTC

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

  3. resolved Feb 09, 2026, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 2, 2026

Episode processing delayed

Detected by Pingoru
Feb 02, 2026, 03:22 PM UTC
Resolved
Feb 02, 2026, 07:31 PM UTC
Duration
4h 9m
Affected: Episode Processing
Timeline · 3 updates
  1. identified Feb 02, 2026, 03:22 PM UTC

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

  2. monitoring Feb 02, 2026, 03:55 PM 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 Feb 02, 2026, 07:31 PM UTC

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

Read the full incident report →

Major January 29, 2026

Zep Retrieval Impacted by Upstream Provider Outage

Detected by Pingoru
Jan 29, 2026, 03:30 AM UTC
Resolved
Jan 29, 2026, 03:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jan 29, 2026, 03:46 AM 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.

Read the full incident report →

Minor December 17, 2025

Latency spikes on episode ingestion endpoints

Detected by Pingoru
Dec 17, 2025, 05:32 PM UTC
Resolved
Dec 17, 2025, 05:47 PM UTC
Duration
15m
Affected: API
Timeline · 2 updates
  1. identified Dec 17, 2025, 05:32 PM UTC

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

  2. resolved Dec 17, 2025, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 15, 2025

Degraded performance on search endpoints

Detected by Pingoru
Dec 15, 2025, 03:47 PM UTC
Resolved
Dec 15, 2025, 06:31 PM UTC
Duration
2h 44m
Affected: API
Timeline · 2 updates
  1. investigating Dec 15, 2025, 03:47 PM 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 Dec 15, 2025, 06:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 8, 2025

Frontend app outage

Detected by Pingoru
Oct 08, 2025, 09:40 PM UTC
Resolved
Oct 08, 2025, 09:47 PM UTC
Duration
6m
Affected: Web App
Timeline · 3 updates
  1. identified Oct 08, 2025, 09:40 PM UTC

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

  2. identified Oct 08, 2025, 09:47 PM UTC

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

  3. resolved Oct 08, 2025, 09:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 2, 2025

Elevated error rate

Detected by Pingoru
Oct 02, 2025, 03:24 PM UTC
Resolved
Oct 02, 2025, 04:11 PM UTC
Duration
46m
Affected: API
Timeline · 2 updates
  1. identified Oct 02, 2025, 03:24 PM UTC

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

  2. resolved Oct 02, 2025, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 16, 2025

Elevated error rates

Detected by Pingoru
Sep 16, 2025, 01:55 AM UTC
Resolved
Sep 16, 2025, 02:08 AM UTC
Duration
13m
Affected: API
Timeline · 2 updates
  1. investigating Sep 16, 2025, 01:55 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 16, 2025, 02:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 5, 2025

Disruption to memory.add and graph.add operations

Detected by Pingoru
Aug 05, 2025, 09:13 PM UTC
Resolved
Aug 05, 2025, 09:13 PM UTC
Duration
Affected: API
Timeline · 1 update
  1. resolved Aug 05, 2025, 09:13 PM 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.

Read the full incident report →