- Detected by Pingoru
- Sep 29, 2026, 06:46 PM UTC
- Resolved
- Sep 30, 2026, 02:43 PM UTC
- Duration
- 19h 56m
Affected: Voice
Timeline · 2 updates
-
monitoring Sep 29, 2026, 06:46 PM UTC
Status: Monitoring Between 2:14 PM and 2:38 PM ET (18:14–18:38 UTC) on September 29, some voice calls could not be connected. The issue has been resolved, and calls are connecting normally. We are continuing to monitor. Affected components Voice (Partial outage)
-
resolved Sep 30, 2026, 02:43 PM UTC
Status: Resolved This is resolved. All systems back to normal Affected components Voice (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 08:04 PM UTC
- Resolved
- Sep 26, 2026, 01:16 AM UTC
- Duration
- 5h 11m
Affected: Agent Designer
Timeline · 2 updates
-
identified Sep 25, 2026, 08:04 PM UTC
Status: Identified Some users may experience intermittent failures logging into Agent Designer. We have identified the issue and expect to have a fix within the next couple of hours. Affected components Agent Designer (Degraded performance)
-
resolved Sep 26, 2026, 01:16 AM UTC
Status: Resolved Authentication issues have been resolved. Affected components Agent Designer (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 04:25 PM UTC
- Resolved
- Sep 15, 2026, 04:25 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 15, 2026, 04:25 PM UTC
Status: Resolved Tickets sent to Smart Relay from any CRM were not answered between 3pm 09/14 and 11:30am. 09/15
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 01:40 AM UTC
- Resolved
- Sep 09, 2026, 02:08 AM UTC
- Duration
- 27m
Affected: 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)
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 11:19 PM UTC
- Resolved
- Sep 01, 2026, 11:29 PM UTC
- Duration
- 10m
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
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)
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 05:26 PM UTC
- Resolved
- Sep 01, 2026, 09:11 PM UTC
- Duration
- 3h 44m
Affected: 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)
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2026, 05:30 AM UTC
- Resolved
- Aug 20, 2026, 04:32 PM UTC
- Duration
- 1d 11h
Affected: 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)
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 09:02 PM UTC
- Resolved
- Aug 11, 2026, 09:29 PM UTC
- Duration
- 27m
Affected: 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)
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 04:29 PM UTC
- Resolved
- Aug 03, 2026, 04:48 PM UTC
- Duration
- 19m
Affected: Voice
Timeline · 4 updates
-
identified Aug 03, 2026, 04:29 PM UTC
Status: Identified Voice is partially down, and some voice calls are impacted, and we are investigating Affected components Voice (Partial outage)
-
identified Aug 03, 2026, 04:30 PM UTC
Status: Identified We have identified the issue, and a fix has been applied. We are verifying the fix. Affected components Voice (Partial outage)
-
monitoring Aug 03, 2026, 04:42 PM UTC
Status: Monitoring We have completed mitigation steps, and the system is currently stable. We are continuing to monitor system health. Affected components Voice (Partial outage)
-
resolved Aug 03, 2026, 04:48 PM UTC
Status: Resolved We have completed monitoring, and the system has remained stable. This incident is now resolved. Affected components Voice (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 01:55 PM UTC
- Resolved
- Jul 21, 2026, 01:55 PM UTC
- Duration
- —
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 1 update
-
resolved Jul 21, 2026, 01:55 PM UTC
Status: Resolved A configuration maintenance caused voice calls to fail for a short period for a small number of customers. The issue was identified and resolved immediately. Resolution: The configuration was corrected and voice calls are operating normally. Affected components Teams (Operational) Knowledge Apps (Operational) JIRA (Operational) Agent Designer (Operational) Voice (Operational) Slack (Operational) Salesforce (Operational) Genesys (Operational) ServiceNow (Operational) Answers (Operational) Email (Operational) SMS (Operational) Intercom (Operational) Front (Operational) Freshdesk (Operational) Chat (Operational) Apps: Other (Operational) Zendesk (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 03:03 PM UTC
- Resolved
- Jul 16, 2026, 03:11 PM UTC
- Duration
- 8m
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 2 updates
-
investigating Jul 16, 2026, 03:03 PM UTC
Status: Investigating We're investigating 500 errors reported on all Maven systems. Affected components Front (Full outage) Salesforce (Full outage) Apps: Other (Full outage) Genesys (Full outage) Agent Designer (Full outage) Answers (Full outage) Teams (Full outage) Freshdesk (Full outage) JIRA (Full outage) ServiceNow (Full outage) Intercom (Full outage) Zendesk (Full outage) Voice (Full outage) SMS (Full outage) Knowledge Apps (Full outage) Chat (Full outage) Email (Full outage) Slack (Full outage)
-
resolved Jul 16, 2026, 03:11 PM UTC
Status: Resolved A bad configuration change caused all Maven systems to suffer a downtime of ~8min. The change was rolled back instantly when the issue was identified, and all systems are back to operational. Affected components SMS (Operational) Slack (Operational) Front (Operational) Salesforce (Operational) Zendesk (Operational) Email (Operational) Teams (Operational) Apps: Other (Operational) Agent Designer (Operational) Genesys (Operational) JIRA (Operational) Answers (Operational) Chat (Operational) Voice (Operational) Intercom (Operational) Knowledge Apps (Operational) Freshdesk (Operational) ServiceNow (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:30 PM UTC
- Resolved
- Jun 10, 2026, 09:24 PM UTC
- Duration
- 2h 53m
Affected: Salesforce
Timeline · 3 updates
-
investigating Jun 10, 2026, 06:30 PM UTC
Status: Investigating Potential timeouts due to degraded API performance Affected components Salesforce (Partial outage)
-
monitoring Jun 10, 2026, 07:52 PM UTC
Status: Monitoring Suspected issues from 3rd party services Affected components Salesforce (Partial outage)
-
resolved Jun 10, 2026, 10:48 PM UTC
Status: Resolved Issue has been resolved Affected components Salesforce (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 03:28 PM UTC
- Resolved
- Jun 10, 2026, 03:28 PM UTC
- Duration
- —
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 1 update
-
resolved Jun 10, 2026, 03:28 PM UTC
Status: Resolved Customers may have experienced intermittent outage caused a third party provider. Issue has since been resolved. Affected components Front (Operational) Genesys (Operational) JIRA (Operational) Zendesk (Operational) Answers (Operational) Chat (Operational) SMS (Operational) Intercom (Operational) Apps: Other (Operational) Freshdesk (Operational) Email (Operational) Teams (Operational) Voice (Operational) Salesforce (Operational) Knowledge Apps (Operational) ServiceNow (Operational) Agent Designer (Operational) Slack (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 01:52 PM UTC
- Resolved
- Jun 10, 2026, 06:26 PM UTC
- Duration
- 4h 33m
Timeline · 4 updates
-
investigating Jun 10, 2026, 01:52 PM UTC
Status: Investigating Documentation sites at docs.mavenagi.com and developers.mavenagi.com are currently unavailable. We're actively investigating the cause. There is no impact to any active production agent traffic or agent operations.
-
resolved Jun 10, 2026, 03:11 PM UTC
Status: Resolved Documentation sites are back up after a fix was pushed by our docs vendor.
-
investigating Jun 10, 2026, 04:29 PM UTC
Status: Investigating Documentations sites are unavailable again, we're working to get them back up.
-
resolved Jun 10, 2026, 06:26 PM UTC
Status: Resolved Documentation sites are now back up.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 02:32 PM UTC
- Resolved
- Jun 08, 2026, 02:32 PM UTC
- Duration
- —
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 1 update
-
resolved Jun 08, 2026, 02:32 PM UTC
Status: Resolved Customers were not able to refresh their knowledge bases that were created from the Google Drive app Affected components SMS (Operational) Front (Operational) Knowledge Apps (Operational) ServiceNow (Operational) Zendesk (Operational) Chat (Operational) Salesforce (Operational) Intercom (Operational) Apps: Other (Operational) Genesys (Operational) Freshdesk (Operational) Answers (Operational) Voice (Operational) Email (Operational) Slack (Operational) Teams (Operational) JIRA (Operational) Agent Designer (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 02:11 PM UTC
- Resolved
- Jun 03, 2026, 02:20 PM UTC
- Duration
- 9m
Affected: Voice
Timeline · 2 updates
-
monitoring Jun 03, 2026, 02:11 PM UTC
Status: Monitoring Starting around 09:00 ET, some voice calls began failing. This is not affecting all voice traffic, but it is causing some impacted calls to end unexpectedly. We have identified the issue and applied a fix around 09:40 ET. All systems should be operating normally now, and we are continuing to monitor for stability. Affected components Voice (Degraded performance)
-
resolved Jun 03, 2026, 02:20 PM UTC
Status: Resolved Confirmed that systems are operating normally. Affected components Voice (Operational)
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 10:40 AM UTC
- Resolved
- May 29, 2026, 12:10 PM UTC
- Duration
- 1h 30m
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 2 updates
-
monitoring May 29, 2026, 10:40 AM UTC
Status: Monitoring We are currently experiencing degraded performance related to an issue with an upstream dependency. Users may notice slower API response times and a small increase in errors. Our team is investigating and will provide updates as they become available. Affected components JIRA (Operational) Answers (Degraded performance) SMS (Operational) Teams (Operational) Front (Operational) Knowledge Apps (Operational) ServiceNow (Operational) Agent Designer (Operational) Voice (Operational) Email (Operational) Slack (Operational) Apps: Other (Operational) Genesys (Operational) Freshdesk (Operational) Chat (Operational) Intercom (Operational) Salesforce (Operational) Zendesk (Operational)
-
resolved May 29, 2026, 12:10 PM UTC
Status: Resolved The issue has been resolved, and performance has returned to normal. Affected components JIRA (Operational) Email (Operational) Apps: Other (Operational) ServiceNow (Operational) Zendesk (Operational) Intercom (Operational) Agent Designer (Operational) Answers (Operational) Slack (Operational) Salesforce (Operational) Freshdesk (Operational) Chat (Operational) SMS (Operational) Teams (Operational) Knowledge Apps (Operational) Genesys (Operational) Front (Operational) Voice (Operational)
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 03:18 PM UTC
- Resolved
- May 20, 2026, 03:18 PM UTC
- Duration
- —
Affected: ChatAnswersVoiceEmailSMSSlackTeamsZendeskSalesforceFreshdeskFrontGenesysServiceNowJIRAIntercomKnowledge AppsApps: OtherAgent Designer
Timeline · 1 update
-
resolved May 20, 2026, 03:18 PM UTC
Status: Resolved Functionality has been restored to the Salesforce app and all systems are fully operational. Affected components Chat (Operational) Apps: Other (Operational) Freshdesk (Operational) JIRA (Operational) Answers (Operational) SMS (Operational) Slack (Operational) Teams (Operational) Intercom (Operational) Front (Operational) Salesforce (Operational) Knowledge Apps (Operational) Agent Designer (Operational) Voice (Operational) Email (Operational) Genesys (Operational) ServiceNow (Operational) Zendesk (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 05:13 PM UTC
- Resolved
- Apr 09, 2026, 06:47 PM UTC
- Duration
- 1h 33m
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 08:39 PM UTC
- Resolved
- Apr 02, 2026, 03:01 AM UTC
- Duration
- 1d 6h
Affected: Answers
Timeline · 6 updates
-
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.
-
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.
-
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.
-
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)
-
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)
-
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 →
- Detected by Pingoru
- Mar 30, 2026, 07:07 PM UTC
- Resolved
- Mar 30, 2026, 07:10 PM UTC
- Duration
- 2m
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 06:07 PM UTC
- Resolved
- Mar 25, 2026, 06:18 PM UTC
- Duration
- 10m
Timeline · 3 updates
-
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.
-
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.
-
resolved Mar 25, 2026, 06:18 PM UTC
Status: Resolved Chat systems are now working as expected
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 05:21 PM UTC
- Resolved
- Mar 25, 2026, 08:48 PM UTC
- Duration
- 1d 3h
Affected: Answers
Timeline · 2 updates
-
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)
-
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 →
- Detected by Pingoru
- Mar 19, 2026, 06:14 PM UTC
- Resolved
- Mar 19, 2026, 06:57 PM UTC
- Duration
- 43m
Affected: Answers
Timeline · 2 updates
-
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)
-
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 →
- Detected by Pingoru
- Mar 19, 2026, 04:46 PM UTC
- Resolved
- Mar 19, 2026, 04:46 PM UTC
- Duration
- —
Read the full incident report →