- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 100
What to do
Check whether your product depends on Gong. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 59m it lasted.
Anything that failed between 2026-08-04 00:30 UTC and 2026-08-04 03:29 UTC may need a replay.Subscribe to Gong's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=gong works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Gong 3
- investigating
We are currently investigating connection failures affecting customers using Gong's MCP integration (including Claude and other MCP-compatible clients).
provider
- identified
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 provide another update as soon as more information becomes available.
provider
- resolved
The issue affecting Gong's MCP integration has been resolved, and all connection routing functionality has returned to normal operations.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-62b43a7b50
Is Gong still down?
No, this incident was resolved 2026-08-04 03:29 UTC. For Gong's live state, see https://down.guide/gong.
How long did it last?
2h 59m, from 2026-08-04 00:30 UTC to 2026-08-04 03:29 UTC, by the times Gong posted.
What caused it?
Gong hasn't published a root cause. If it does, it shows here.
Where does this come from?
Gong's official status page, https://status.gong.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.