Maven AGI Outage History

Maven AGI is up right now

There were 14 Maven AGI outages since February 12, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.mavenagi.com

Minor April 15, 2026

Voice escalations were not executing

Detected by Pingoru
Apr 15, 2026, 12:12 AM UTC
Resolved
Apr 15, 2026, 12:12 AM UTC
Duration
—
Affected: AnswersAgent Designer
Timeline · 3 updates
  1. identified Mar 19, 2026, 03:27 PM UTC

    Status: Identified Users were able to have normal conversations with Maven Voice, but were not able to escalate to a human agent. Affected components Agent Designer (Operational) Answers (Operational)

  2. resolved Mar 19, 2026, 04:46 PM UTC

    Status: Resolved User now able to escalate Affected components Agent Designer (Operational) Answers (Operational)

  3. resolved Apr 15, 2026, 12:12 AM UTC

    Status: Resolved On March 19 between approximately 11:10 AM and 12:47 PM ET, a subset of voice calls on the Maven platform failed to escalate. Other voice functionality, including call answering, agent interaction, and in-call handling, continued to operate normally, and text-based channels were unaffected. The cause was a regression in a routine deployment to one of the integration components that handles voice escalation. An on-call engineer identified the issue and shipped a corrected release at approximately 12:40 PM ET, with escalation flows confirmed restored by 12:47 PM ET. The regression slipped through because our integration layer, the components that connect Maven to specific voice and telephony providers, did not have the same level of pre-production validation and production monitoring as our core platform. That gap is on us, and we're closing it. To prevent a recurrence, we are standing up a dedicated staging environment for voice integration components with real end-to-end escalation tests gating every release, adding production alerting and monitoring on the integration layer so anomalies are caught in minutes rather than by customer reports, and introducing fallback routing so a failure on the primary escalation path does not fail the call outright. Going forward, changes to these components will also be deployed outside of peak call-volume hours. We know voice escalation is a high-trust path. When a customer needs a human, nothing else matters. We're sorry for the disruption and appreciate your patience. If you'd like to discuss the incident or the remediation plan in more detail, please reach out to your account team directly. Affected components Agent Designer (Operational) Answers (Operational)

Read the full incident report →

Minor April 9, 2026

Reduced connection and timeouts for API calls

Detected by Pingoru
Apr 09, 2026, 06:47 PM UTC
Resolved
Apr 09, 2026, 06:47 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Apr 09, 2026, 04:04 PM UTC

    Status: Investigating The connection issues and timeouts have been mitigated and we've identified probably root causes, which we will start rolling out.

  2. identified Apr 09, 2026, 05:16 PM UTC

    Status: Identified We've identified the root causes and are pushing out the fixes now. The prior mitigation work has removed the impact from the affected components.

  3. resolved Apr 09, 2026, 06:47 PM UTC

    Status: Resolved The fix for the connectivity and timing issues has been deployed and verified.

Read the full incident report →

Minor April 2, 2026

Knowledge ingestion responsiveness issues

Detected by Pingoru
Apr 02, 2026, 03:01 AM UTC
Resolved
Apr 02, 2026, 03:01 AM UTC
Duration
—
Affected: Answers
Timeline · 6 updates
  1. investigating Mar 31, 2026, 08:39 PM UTC

    Status: Investigating We are seeing unresponsiveness or slowness in knowledge base creation possibly due to a spike in related workflows; we are investigating the root cause.

  2. identified Mar 31, 2026, 09:47 PM UTC

    Status: Identified We have identified specific database settings that have led to suboptimal performance in high ingestion loads; these have been changed and released to production. Ingestion jobs are still backed off but we see faster completions of these jobs. We continue to monitor the process.

  3. monitoring Mar 31, 2026, 11:47 PM UTC

    Status: Monitoring We've pushed out a release that included changes decreasing the db load, and the system has recovered as expected.

  4. monitoring Apr 01, 2026, 04:14 PM UTC

    Status: Monitoring Current state: • Knowledge base edits and new documents added today are being indexed normally for the majority of customers. • Some changes made yesterday may not yet be fully reflected. As a quick workaround, making a small edit to a knowledge base will trigger reindexing. • Customers with very large knowledge bases (many hundreds of documents) may still experience delays. A targeted fix is currently being deployed and expected to be live within the next few hours. Affected components Answers (Degraded performance)

  5. monitoring Apr 01, 2026, 06:52 PM UTC

    Status: Monitoring We believe we’ve resolved the issues and are monitoring to confirm. We expect all affected KBs to be fixed within eight hours. Affected components Answers (Degraded performance)

  6. resolved Apr 02, 2026, 03:01 AM UTC

    Status: Resolved The publishing delay has been resolved, and all previously affected knowledge bases have been restored. Affected components Answers (Operational)

Read the full incident report →

Minor March 30, 2026

Agent Designer Unreachable

Detected by Pingoru
Mar 30, 2026, 07:10 PM UTC
Resolved
Mar 30, 2026, 07:10 PM UTC
Duration
—
Affected: Agent Designer
Timeline · 2 updates
  1. investigating Mar 30, 2026, 06:40 PM UTC

    Status: Investigating We are aware that Agent Designer is currently unreachable and our team is actively investigating. Affected components Agent Designer (Full outage)

  2. resolved Mar 30, 2026, 07:10 PM UTC

    Status: Resolved Agent designer issues have been resolved and the application should be working as expected now. Affected components Agent Designer (Operational)

Read the full incident report →

Minor March 25, 2026

Investigating increased ask latency

Detected by Pingoru
Mar 25, 2026, 08:48 PM UTC
Resolved
Mar 25, 2026, 08:48 PM UTC
Duration
—
Affected: Answers
Timeline · 2 updates
  1. investigating Mar 24, 2026, 05:21 PM UTC

    Status: Investigating We are experiencing some service latency and we are actively investigating. Affected components Answers (Degraded performance)

  2. resolved Mar 25, 2026, 08:48 PM UTC

    Status: Resolved The elevated latency issue has been resolved. Affected components Answers (Operational)

Read the full incident report →

Minor March 25, 2026

Update: Chat window issue

Detected by Pingoru
Mar 25, 2026, 06:18 PM UTC
Resolved
Mar 25, 2026, 06:18 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 25, 2026, 06:07 PM UTC

    Status: Investigating Update: Chat Window Issue Some users may have experienced issues with chat window. A fix has been deployed, and we are actively monitoring the system to ensure stability. We will continue to share updates as needed.

  2. monitoring Mar 25, 2026, 06:10 PM UTC

    Status: Monitoring Update: Chat Issue Some users may have experienced issues with chat window. A fix has been deployed, and we are actively monitoring the system to ensure stability. We will continue to share updates as needed.

  3. resolved Mar 25, 2026, 06:18 PM UTC

    Status: Resolved Chat systems are now working as expected

Read the full incident report →

Minor March 19, 2026

Increased API chat latencies

Detected by Pingoru
Mar 19, 2026, 06:57 PM UTC
Resolved
Mar 19, 2026, 06:57 PM UTC
Duration
—
Affected: Answers
Timeline · 2 updates
  1. investigating Mar 19, 2026, 06:14 PM UTC

    Status: Investigating We are aware and investigating an increase in chat latencies and timeouts Affected components Answers (Degraded performance)

  2. resolved Mar 19, 2026, 06:57 PM UTC

    Status: Resolved Latency issues have been resolved. We will continue to implement improvements to help prevent recurrence. Affected components Answers (Operational)

Read the full incident report →

Minor March 16, 2026

Voice Calls are Down

Detected by Pingoru
Mar 16, 2026, 11:21 PM UTC
Resolved
Mar 16, 2026, 11:21 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 16, 2026, 10:53 PM UTC

    Status: Investigating We are currently experiencing a major incident where all voice calls are down. The team is actively investigating the issue.

  2. identified Mar 16, 2026, 11:08 PM UTC

    Status: Identified We have identified the issue and are actively working on a fix.

  3. resolved Mar 16, 2026, 11:21 PM UTC

    Status: Resolved The issue is now resolved and voice calls are processed again.

Read the full incident report →

Minor March 13, 2026

Cannot add documents to newly created Manual KnowledgeBases

Detected by Pingoru
Mar 13, 2026, 09:46 PM UTC
Resolved
Mar 13, 2026, 09:46 PM UTC
Duration
—
Affected: Agent Designer
Timeline · 2 updates
  1. identified Mar 13, 2026, 08:34 PM UTC

    Status: Identified For Manual Knowledge Bases created in the last few days, there's no mechanism to add documents to them. The problem has been identified and the fix is implemented, which we will verify and deploy next Monday. Affected components Agent Designer (Degraded performance)

  2. resolved Mar 13, 2026, 09:46 PM UTC

    Status: Resolved This issue has been resolved. Affected components Agent Designer (Operational)

Read the full incident report →

Minor February 19, 2026

Experiencing delays in processing

Detected by Pingoru
Feb 19, 2026, 05:24 PM UTC
Resolved
Feb 19, 2026, 05:24 PM UTC
Duration
—
Affected: AnswersAgent Designer
Timeline · 6 updates
  1. identified Feb 12, 2026, 06:46 PM UTC

    Status: Identified Message processing is currently delayed, so response times may be slower than usual. We’re actively working on solutions and appreciate your patience. Affected components Agent Designer (Degraded performance) Answers (Degraded performance)

  2. identified Feb 12, 2026, 09:29 PM UTC

    Status: Identified The implemented mitigations are proving effective, and the backlog is gradually being reduced. While we have not yet reached a state of complete resolution, we are moving in a positive direction. Affected components Agent Designer (Degraded performance) Answers (Degraded performance)

  3. monitoring Feb 13, 2026, 12:34 AM UTC

    Status: Monitoring Additional mitigations have been implemented that significantly contributed to alleviating the backlog. Although some delays persist, it is anticipated that these will be resolved within an hour or so. Affected components Agent Designer (Degraded performance) Answers (Degraded performance)

  4. monitoring Feb 13, 2026, 08:41 PM UTC

    Status: Monitoring We're still seeing some delays in the processing pipeline and are working to smooth everything out before resolving this issue. Affected components Agent Designer (Degraded performance) Answers (Degraded performance)

  5. monitoring Feb 15, 2026, 09:06 PM UTC

    Status: Monitoring All delays were resolved Friday evening and have not reoccurred. We will continue to monitor the situation and mark it as resolved next week once we confirm that normal traffic patterns are unaffected. Affected components Agent Designer (Degraded performance) Answers (Degraded performance)

  6. resolved Feb 19, 2026, 05:24 PM UTC

    Status: Resolved Our backend processing delays have been fully resolved, and the system is operating normally again. Affected components Agent Designer (Operational) Answers (Operational)

Read the full incident report →

Minor February 13, 2026

Knowledge base creation via crawls is currently unavailable

Detected by Pingoru
Feb 13, 2026, 08:38 PM UTC
Resolved
Feb 13, 2026, 08:38 PM UTC
Duration
—
Affected: Agent Designer
Timeline · 2 updates
  1. investigating Feb 13, 2026, 08:00 PM UTC

    Status: Investigating We're currently unable to create or refresh a knowledge base via crawl because of an issue with our provider. We're sorry for the inconvenience and are working to resolve it as quickly as possible. Affected components Agent Designer (Degraded performance)

  2. resolved Feb 13, 2026, 08:38 PM UTC

    Status: Resolved Our provider has resolved the issue and crawls are working again. Any previously scheduled crawls were not canceled and will still run. Affected components Agent Designer (Operational)

Read the full incident report →

Looking to track Maven AGI downtime and outages?

Pingoru polls Maven AGI's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Maven AGI reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Maven AGI alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Maven AGI for free

5 free monitors · No credit card required