- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 20of 100
What to do
Check whether you use Gong in us. 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 40m it lasted.
Anything that failed between 2026-06-16 12:15 UTC and 2026-06-16 12:55 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 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 soon as more information becomes available.
provider
- monitoring
We have implemented a fix and are currently monitoring system performance.
provider
- resolved
The incident has been resolved
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-def486c2b8
Is Gong still down?
No, this incident was resolved 2026-06-16 12:55 UTC. For Gong's live state, see https://down.guide/gong.
How long did it last?
40m, from 2026-06-16 12:15 UTC to 2026-06-16 12:55 UTC, by the times Gong posted.
What was affected?
Gong named in us.
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.