Gong

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 18:54 UTC

   We are currently investigating an issue affecting Gong Email activity. Users may experience delays or partial failures with emails being indexed and synced to their CRM.

2. investigating 2026-10-08 18:57 UTC

   We are currently investigating an issue affecting Gong Email activity. Users may experience delays or partial failures with emails being indexed and synced to their CRM & Engage Analytics.

3. identified 2026-10-08 20:57 UTC

   We identified the issue and now working on a fix

4. resolved 2026-10-09 00:05 UTC

   **Resolved** – The issue affecting email activity syncing has been resolved. We are currently monitoring the system as remaining updates process. Some users may experience brief delays in syncing as data catches up.

5. resolved 2026-10-09 08:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 12:28 UTC

   We're investigating an issue causing Gong Enrich to be unavailable. Our teams are aware and working on it. We'll provide another update as soon as we have more information

2. monitoring 2026-10-08 12:51 UTC

   We have implemented a fix for the issue affecting Gong Enrich, and our team is now monitoring system performance to confirm the service is operating as expected. We will provide another update once we have confirmed full recovery.

3. resolved 2026-10-08 14:01 UTC

   The issue has been resolved

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-10-05 13:12 UTC

   We have implemented a fix and are currently monitoring system performance.

2. resolved 2026-10-06 06:48 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 11:18 UTC

   We are currently investigating an issue affecting Engage. Users may experience issues accessing or using the To-dos page. We will provide another update as soon as we have more information.

2. identified 2026-10-05 11:29 UTC

   We have identified the issue affecting Engage. Users may experience issues accessing or using the To-dos page. We are currently applying a fix to resolve the issue. We will provide another update as soon as more information becomes available.

3. monitoring 2026-10-05 13:04 UTC

   We have implemented a fix and are currently monitoring system performance across all cells.

4. resolved 2026-10-05 13:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-28 15:34 UTC

   We've detected an issue with the gong dialer and are actively investigating

2. investigating 2026-09-28 15:38 UTC

   We've detected an issue with the gong dialer and are actively investigating

3. identified 2026-09-28 16:25 UTC

   We have identified the cause of the issue affecting the Gong dialer and actively working on a fix

4. monitoring 2026-09-28 16:30 UTC

   We have implemented a fix and are currently monitoring system performance.

5. resolved 2026-09-28 16:49 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-16 11:52 UTC

   **Investigating:** Our team continues to investigate the issue affecting multiple Gong components, including Forecast, Flows, and the Call page. Users may experience loading issues and errors when accessing these areas or performing certain actions. Please check back for updates.

2. identified 2026-09-16 14:29 UTC

   We identified a frontend regression introduced by a recent migration. We are working to revert the affected change and restore the service. Please check back for updates.

3. resolved 2026-09-16 14:51 UTC

   The issue has been resolved. We reverted the affected frontend change, and the impacted pages are now functioning as expected. Thank you for your patience.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-16 09:24 UTC

   We have identified an issue affecting CRM, due to a third-party service provider, Salesforce, degradation. All users with Salesforce CRM integration may experience delayed data updates across Deal Board, Forecast, Enrich, AI fields and Engage. There is no loss of data. We are...

2. monitoring 2026-09-16 10:40 UTC

   We are working to ensure service is fully restored for all customers. Please check back for updates.

3. monitoring 2026-09-16 11:34 UTC

   We are currently monitoring system recovery following an update from our third-party service provider (Salesforce), who has begun rolling out a fix. Users with Salesforce CRM integration may still experience delayed data updates across Deal Board, Forecast, and Engage as service...

4. resolved 2026-09-16 22:05 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 20:27 UTC

   We are currently investigating an issue affecting Data capture & recording. Users in the US-hosted environment may experience delays in call processing (~20 minutes for video calls, ~70 minutes for audio calls). We will provide another update in 30 minutes.

2. investigating 2026-09-09 21:08 UTC

   Our team continues to investigate the issue affecting Data Capture & Processing. Please check back for updates.

3. investigating 2026-09-10 09:26 UTC

   We are currently not observing any active errors across our services. However, our engineering team is continuing to investigate the underlying issue to pinpoint the root cause and ensure complete stability. We will provide further updates as more information becomes available.

4. resolved 2026-09-10 16:06 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-09 17:57 UTC

   We are investigating a database issue tat is having impact on the Gong Anywhere extension, resulting in the UI overlays not to be rendered in Gmail / SFDC / Dynamics.

2. monitoring 2026-09-09 18:09 UTC

   A fix was implemented to restore Gong Anywhere Extension and our team is monitoring.

3. resolved 2026-09-09 18:40 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-08 20:35 UTC

   We have identified an issue affecting Engage (People) and the Gong Anywhere Chrome extension. A subset of users in the US-hosted environment may experience display and loading issues on the People page, as well as contact overlay details failing to render in the extension. We...

2. resolved 2026-09-08 23:02 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 18:10 UTC

   Users may be experiencing disruptions with Engage Accounts. Our teams are working quickly to investigate and address the issue.

2. investigating 2026-09-08 18:18 UTC

   Users may be experiencing disruptions with Engage Accounts. Our teams are working quickly to investigate and address the issue.

3. resolved 2026-09-08 19:07 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 00:30 UTC

   We are currently investigating connection failures affecting customers using Gong's MCP integration (including Claude and other MCP-compatible clients).

2. identified 2026-08-04 01:29 UTC

   We have identified the issue affecting Gong's MCP integration. Customers using Gong's MCP integration (including Claude and other MCP-compatible clients) may experience connection failures and failed tool call requests. We are currently working on deploying a fix and will...

3. resolved 2026-08-04 03:29 UTC

   The issue affecting Gong's MCP integration has been resolved, and all connection routing functionality has returned to normal operations.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 08:46 UTC

   We are currently investigating an issue affecting access to the Gong application. Impact: Users across all environments may experience sign-in failures or authentication timeouts. Status: Our engineering team is actively investigating the root cause. Next Update: We will provide...

2. investigating 2026-07-27 08:54 UTC

   We are currently investigating an issue affecting access to the Gong application. Impact: Users across all environments attempting to sign in using Office 365 may experience sign-in failures or authentication timeouts. Status: Our engineering team is actively investigating the...

3. identified 2026-07-27 09:18 UTC

   We have identified the issue affecting the Gong app. A subset of users across all environments attempting to sign in using Office 365 may experience sign-in failures or authentication timeouts. We are currently working on a fix. We will provide another update as soon as more...

4. resolved 2026-07-27 10:05 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-21 21:03 UTC

   We have identified the issue affecting call processing. Users in the US may experience delays in call processing. Fix have been deployed. Next update in 30 minutes.

2. monitoring 2026-07-21 21:37 UTC

   We have implemented a fix and are currently monitoring system performance.

3. resolved 2026-07-21 22:14 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-14 14:33 UTC

   We are investigating reports of issues with the Gong extension and are working to resolve them for affected users.

2. identified 2026-07-14 16:27 UTC

   We have identified the issue affecting the Gong extension (specifically version 1.0.76). A subset of Salesforce users may experience issues with the extension being unresponsive or failing to load. We are currently deploying a fix, which we estimate will be available for all...

3. resolved 2026-07-15 04:00 UTC

   The issue affecting the Gong extension has been fully resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 10:45 UTC

   We experienced an issue affecting the Gong platform. Our engineering team successfully mitigated the impact and restored full service. We are now investigating the root cause to prevent similar issues in the future.

2. resolved 2026-07-13 10:48 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-12 09:27 UTC

   We are currently experiencing an issue affecting the Gong platform. Our engineering team is actively investigating the root cause and working to mitigate the impact to restore full service as quickly as possible.

2. resolved 2026-07-12 09:59 UTC

   Gong platform is fully operational.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 05:05 UTC

   We’re investigating an issue where the Team Insights page is failing to load. Some customers may be unable to load the Team Insights page while we work on a fix. Next update will be shared as we learn more.

2. resolved 2026-07-01 05:22 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-29 13:31 UTC

   We are currently investigating an issue causing delayed event synchronization to the CRM. This is a limited-scope incident, and our engineering team is actively working to identify the root cause. We will provide another update as soon as more information becomes available.

2. investigating 2026-06-29 17:27 UTC

   We are continuing to investigate an issue causing delayed event synchronization to the CRM. A subset of users in the US-hosted environment may experience delays with CRM synchronization. Our engineering team is actively working to identify the root cause, and we will provide...

3. identified 2026-06-29 19:55 UTC

   We have identified the issue causing the CRM synchronization delays. A subset of users in the US-hosted environment may continue to experience delays with CRM event synchronization. We are currently actively working to resolve the issue. Next update as soon as more information...

4. monitoring 2026-07-01 15:49 UTC

   We identified and resolved the issue that caused delays in exporting activities from Gong to CRM systems. Some customers may still experience delays while the backlog is being processed. Delayed activities will be automatically exported to your CRM, and no action is required on...

5. monitoring 2026-07-01 16:06 UTC

   We identified and resolved the issue that caused delays in exporting activities from Gong to CRM systems. Some customers may still experience delays while the backlog is being processed. Delayed activities will be automatically exported to your CRM, and no action is required on...

6. resolved 2026-07-02 20:21 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2026-06-22 14:40 UTC

   We have isolated the issue affecting the Web app. A **Cloudflare** outage is causing login failures for a subset of users in the US-hosted environment. Cloudflare is currently working on a fix, and we are monitoring the situation until full connectivity is restored.

2. resolved 2026-06-22 22:21 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 12:15 UTC

   We are currently investigating an issue affecting the Call page. Users in the US-hosted environment may experience issues where they are unable to play recorded meetings. Our engineering teams are actively working to identify the root cause. We will provide another update as...

2. monitoring 2026-06-16 12:50 UTC

   We have implemented a fix and are currently monitoring system performance.

3. resolved 2026-06-16 12:55 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-15 17:02 UTC

   **Investigating:** Our Google app has lost access, preventing sending and ingesting of email and calendar events. Customers are experiencing errors when trying to send emails, connect Google, and perform related actions. We are investigating the root cause

2. resolved 2026-06-15 18:40 UTC

   **Problem**: Our Google app lost access, preventing all read and write operations for email and calendar integrations. **Impact**: Customers were unable to send emails, connect their Google accounts, or sync calendar events due to a complete loss of Google integration access....

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 11:01 UTC

   We are currently investigating an issue affecting users to generate meeting links through Google calendar within the Consent application. Our team is actively working to identify the root cause and restore functionality as quickly as possible.

2. monitoring 2026-06-10 12:05 UTC

   A fix has been implemented, and we are seeing signs of recovery, please refresh your browser. Users should now be able to generate meeting links through the Google Add-in within the Consent application. We are continuing to monitor the service closely to ensure stability and...

3. resolved 2026-06-10 20:36 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-09 14:55 UTC

   We have identified the issue affecting the Admin center. Administrators may experience technical errors or incorrect routing when clicking the button to access the admin center. We are currently deploying a fix to resolve this behavior. Next update in 40 minutes.

2. resolved 2026-06-09 15:48 UTC

   The issue affecting the Admin center has been resolved. Administrators are now able to successfully navigate to the admin center without encountering URL or routing errors.

3. monitoring 2026-06-09 19:33 UTC

   We're still working on a fix. Some pages within the admin center may not be accessible.

4. resolved 2026-06-09 22:46 UTC

   The issue has been fully resolved.

Excerpts are shortened. Read the full incident on Gong's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-03 14:35 UTC

   We are actively tracking a widespread outage with Webex. As a result, some users may experience difficulties joining or hosting their own meetings. Additionally, this outage is impacting our call recording system, causing a limited number of customer calls to fail to record. We...

2. resolved 2026-06-03 17:44 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Gong's status page.