- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 38of 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 32m it lasted.
Anything that failed between 2026-07-12 09:27 UTC and 2026-07-12 09:59 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 2
- investigating
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.
provider
- resolved
Gong platform is fully operational.
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-e0871730bc
Is Gong still down?
No, this incident was resolved 2026-07-12 09:59 UTC. For Gong's live state, see https://down.guide/gong.
How long did it last?
32m, from 2026-07-12 09:27 UTC to 2026-07-12 09:59 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.