G
Outage recap · Gong

Gong outage — September 8, 2026

On September 8, 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.

We are currently experiencing issues with Engage Accounts

minor
Started
Sep 8, 2:10 PM EDT
Resolved
Sep 8, 3:07 PM EDT
Duration
56 min

Gong's updates (3)

  1. investigating · Sep 8, 2:10 PM EDT

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

  2. investigating · Sep 8, 2:18 PM EDT

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

  3. resolved · Sep 8, 3:07 PM EDT

    The issue has been resolved.

What our checks recorded

We checked Gong 11 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 202 ms, against 176 ms over the 24 hours before. Gong posted the incident at Sep 8, 2:10 PM EDT.

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

Engage & Web App - Degraded Performance

minor
Started
Sep 8, 4:35 PM EDT
Resolved
Sep 8, 7:02 PM EDT
Duration
2h 26m

Gong's updates (2)

  1. identified · Sep 8, 4:35 PM EDT

    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 are currently working to mitigate the issue.

  2. resolved · Sep 8, 7:02 PM EDT

    The issue has been resolved.

What our checks recorded

We checked Gong 29 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 234 ms, against 176 ms over the 24 hours before. Gong posted the incident at Sep 8, 4:35 PM 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.