Is Maven AGI down?

Last checked 8m ago
Current status
Maven AGI is up

No incidents right now.

Official status page: https://status.mavenagi.com · Polled every 5 minutes · 22 components tracked

Maven AGI is operational right now. Last checked 8m ago; the most recent incident resolved 6d ago.

Real-time Maven AGI status, recent outages, and incident history — pulled directly from Maven AGI's official status page at https://status.mavenagi.com every 5 minutes. Pingoru tracks 22 Maven AGI services and has captured 8 incidents in the last 90 days (96.97% uptime). Get email, Slack, Discord, or webhook alerts the moment Maven AGI reports a new incident — free for 5 monitors, no credit card.

Users who monitor Maven AGI also follow these Communications services: GoDaddy Miro Talkdesk GoToConnect SMTP2GO Singlewire Software Slido HelpScout Nuance Flowroute View all 6,000+ providers
Maven AGI uptime 96.97% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 09, 2026, 02:08 AM UTC · Resolved Sep 09, 2026, 02:08 AM UTC
    Answers
    Timeline · 4 updates
    • investigating · Sep 09, 2026, 01:40 AM UTC

      Status: Investigating We are investigating increased error rates affecting the conversation endpoint. We will provide an update as more information becomes available. Affected components Answers (Degraded performance)

    • identified · Sep 09, 2026, 01:49 AM UTC

      Status: Identified We believe we have identified the problem and are taking steps to resolve. Affected components Answers (Degraded performance)

    • monitoring · Sep 09, 2026, 01:56 AM UTC

      Status: Monitoring We have taken steps to remediate the problem. Currently monitoring to make sure everything is healthy. Affected components Answers (Degraded performance)

    • resolved · Sep 09, 2026, 02:08 AM UTC

      Status: Resolved Conversation endpoint is determined to be in a healthy state Affected components Answers (Operational)

    Latest: Status: Resolved Conversation endpoint is determined to be in a healthy state Affected components Answers (Operational)

  2. Resolved
    Started Sep 03, 2026, 09:11 PM UTC · Resolved Sep 03, 2026, 09:11 PM UTC
    Voice
    Timeline · 4 updates
    • identified · Sep 01, 2026, 05:26 PM UTC

      Status: Identified Some voice calls are failing when transferring to a live agent. This is caused by an ongoing incident with a third-party provider, who has confirmed the issue and is deploying a fix. Most transfers are completing normally, and no other voice functionality is affected. We will post another update by 18:00 UTC. Affected components Voice (Partial outage)

    • monitoring · Sep 01, 2026, 05:59 PM UTC

      Status: Monitoring No failures since 17:27 UTC (28 min clean). Not calling it resolved yet because the third-party provider still has their incident on monitoring, not resolved. Provider status: 502 REST API incident → monitoring at 17:40 UTC ("now operating normally"). Their Voice REST API incident → resolved 17:42 UTC. Next provider update expected ~18:10 UTC. Staying in monitoring until they mark resolved. Will close after that. Impact numbers and follow-ups to come. Affected components Voice (Partial outage)

    • monitoring · Sep 01, 2026, 06:57 PM UTC

      Status: Monitoring Third-party provider cleared the incident] — Our last failure was 17:27 UTC, so 87 minutes clean with 324 successful transfers since. Failure rate back to baseline. Affected components Voice (Operational)

    • resolved · Sep 03, 2026, 09:11 PM UTC

      Status: Resolved All systems are operating normally. Affected components Voice (Operational)

    Latest: Status: Resolved All systems are operating normally. Affected components Voice (Operational)

  3. Resolved
    Started Sep 01, 2026, 11:29 PM UTC · Resolved Sep 01, 2026, 11:29 PM UTC
    ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdesk
    Timeline · 3 updates
    • investigating · Sep 01, 2026, 11:19 PM UTC

      Status: Investigating Our monitoring detected elevated error rates affecting API requests and agent responses, beginning at approximately 7:14 PM ET. Affected requests returned errors rather than completing slowly. Engineers were engaged and began investigating immediately. Affected components Agent Designer (Degraded performance) Email (Degraded performance) Teams (Degraded performance) Intercom (Degraded performance) Salesforce (Degraded performance) Genesys (Degraded performance) JIRA (Degraded performance) Chat (Degraded performance) Front (Degraded performance) Zendesk (Degraded performance) Answers (Full outage) Voice (Degraded performance) Slack (Degraded performance) Apps: Other (Degraded performance) Knowledge Apps (Degraded performance) SMS (Degraded performance) Freshdesk (Degraded performance) ServiceNow (Degraded performance)

    • identified · Sep 01, 2026, 11:23 PM UTC

      Status: Identified We identified the cause as a structural database change included in a routine platform update. Completing that change required locking a core data table, and incoming requests queued behind the lock until the system could no longer accept new work. The operation completed at approximately 7:22 PM ET and error rates began recovering. Affected components Intercom (Degraded performance) Knowledge Apps (Degraded performance) Answers (Full outage) Voice (Degraded performance) Genesys (Degraded performance) Freshdesk (Degraded performance) ServiceNow (Degraded performance) Zendesk (Degraded performance) Email (Degraded performance) Slack (Degraded performance) Teams (Degraded performance) Front (Degraded performance) Salesforce (Degraded performance) Apps: Other (Degraded performance) JIRA (Degraded performance) Agent Designer (Degraded performance) Chat (Degraded performance) SMS (Degraded performance)

    • resolved · Sep 01, 2026, 11:29 PM UTC

      Status: Resolved Service returned to normal performance at approximately 7:29 PM ET. Total impact lasted approximately nine minutes, including about five minutes of sustained request failures. The update that triggered the issue completed successfully, and no customer data was lost or affected. Affected components Teams (Operational) Intercom (Operational) Genesys (Operational) Freshdesk (Operational) ServiceNow (Operational) Agent Designer (Operational) Chat (Operational) SMS (Operational) Slack (Operational) Front (Operational) Apps: Other (Operational) Answers (Operational) Email (Operational) Salesforce (Operational) Knowledge Apps (Operational) Voice (Operational) JIRA (Operational) Zendesk (Operational)

    Latest: Status: Resolved Service returned to normal performance at approximately 7:29 PM ET. Total impact lasted approximately nine minutes, including about five minutes of sustained reque…

  4. Resolved
    Started Aug 20, 2026, 04:32 PM UTC · Resolved Aug 20, 2026, 04:32 PM UTC
    Chat
    Timeline · 2 updates
    • identified · Aug 19, 2026, 05:30 AM UTC

      Status: Identified A small percentage of customers are not able to load the chat widget into their browser. Affected components Chat (Partial outage)

    • resolved · Aug 20, 2026, 04:32 PM UTC

      Status: Resolved This issue has been resolved - a small percentage of customers were not able to load or use the Maven chat widget. Affected components Chat (Operational)

    Latest: Status: Resolved This issue has been resolved - a small percentage of customers were not able to load or use the Maven chat widget. Affected components Chat (Operational)

  5. Resolved
    Started Aug 11, 2026, 09:29 PM UTC · Resolved Aug 11, 2026, 09:29 PM UTC
    Apps: Other
    Timeline · 2 updates
    • identified · Aug 11, 2026, 09:02 PM UTC

      Status: Identified Authentication Errors Occurring Affected components Apps: Other (Partial outage)

    • resolved · Aug 11, 2026, 09:29 PM UTC

      Status: Resolved An expired authentication credential prevented the Microsoft Teams integration from connecting to Microsoft's platform. The credential has been rotated and the integration is now fully operational. Affected components Apps: Other (Operational)

    Latest: Status: Resolved An expired authentication credential prevented the Microsoft Teams integration from connecting to Microsoft's platform. The credential has been rotated and the int…

See the full Maven AGI outage history

3 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Maven AGI outage history →

Or sign up free to get alerts when Maven AGI breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 8 incidents View full outage history →