Gong: Dialer - Degraded Performance

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 1h 15m it lasted.
Anything that failed between 2026-09-28 15:34 UTC and 2026-09-28 16:49 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.

investigatingSep 28, 2026, 3:34 PM UTC
We've detected an issue with the gong dialer and are actively investigating
provider
investigatingSep 28, 2026, 3:38 PM UTC
We've detected an issue with the gong dialer and are actively investigating
provider
identifiedSep 28, 2026, 4:25 PM UTC
We have identified the cause of the issue affecting the Gong dialer and actively working on a fix
provider
monitoringSep 28, 2026, 4:30 PM UTC
We have implemented a fix and are currently monitoring system performance.
provider
resolvedSep 28, 2026, 4:49 PM UTC
The issue has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Gong still down?

No, this incident was resolved 2026-09-28 16:49 UTC. For Gong's live state, see https://down.guide/gong.

How long did it last?

1h 15m, from 2026-09-28 15:34 UTC to 2026-09-28 16:49 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.