G
Outage recap · Gong

Gong outage — October 5, 2026

On October 5, 2026, Gong had 2 reported incidents on Gong's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Engage - To-dos Service Disruption

major
Started
Oct 5, 7:18 AM EDT
Resolved
Oct 5, 9:28 AM EDT
Duration
2h 9m

Gong's updates (4)

  1. investigating · Oct 5, 7:18 AM EDT

    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 · Oct 5, 7:29 AM EDT

    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 · Oct 5, 9:04 AM EDT

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

  4. resolved · Oct 5, 9:28 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Gong 26 times from Gong's start time to its resolution, once every five minutes. Every one of them reached Gong's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 158 ms, against 174 ms over the 24 hours before. Gong posted the incident at Oct 5, 7:18 AM EDT.

Updates are Gong's own words from its status page (status: resolved); we never add an inferred cause.

People, Flows, and Gong Extension - Service disruption

minor
Started
Oct 5, 9:12 AM EDT
Resolved
Oct 6, 2:48 AM EDT
Duration
17h 37m

Gong's updates (2)

  1. monitoring · Oct 5, 9:12 AM EDT

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

  2. resolved · Oct 6, 2:48 AM EDT

    The issue has been resolved.

What our checks recorded

We checked Gong 211 times from Gong's start time to its resolution, once every five minutes. Every one of them reached Gong's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 175 ms, against 175 ms over the 24 hours before. Gong posted the incident at Oct 5, 9:12 AM EDT.

Updates are Gong's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Gong. This recap summarizes incidents published on Gong's official status page.