Skip to main content
Gong logo

Is Gong Down?

No — Gong is up

Reachable from all 8 checked regions

Average response time: 258ms

Last checked · checks run every 6 hours

Official status page: https://status.gong.io

Gong uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
258ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 8 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom
135ms
DNS 1ms TCP 2ms TLS 12ms TTFB 111ms
cdg
196ms
DNS 0ms TCP 5ms TLS 12ms TTFB 146ms
dfw
146ms
DNS 0ms TCP 1ms TLS 20ms TTFB 132ms
ewr
93ms
DNS 0ms TCP 1ms TLS 13ms TTFB 82ms
fra
93ms
DNS 2ms TCP 1ms TLS 8ms TTFB 77ms
gru
373ms
DNS 0ms TCP 1ms TLS 10ms TTFB 348ms
iad
81ms
DNS 1ms TCP 0ms TLS 7ms TTFB 72ms
jnb
793ms
DNS 2ms TCP 0ms TLS 7ms TTFB 752ms
lax
100ms
DNS 4ms TCP 1ms TLS 17ms TTFB 85ms

What Gong does

Gong records and analyses customer conversations across calls, meetings and email, turning them into coaching material and pipeline forecasts. Sales organisations rely on it to capture calls automatically, so the costly failure is not the dashboard being unavailable but a customer conversation that was never recorded at all.

What an outage looks like

The web application fails to load or shows an empty activity feed. Calls take place normally but do not appear afterwards, which is only discovered when someone goes looking for the recording. Transcription and analysis lag behind, so recent calls exist without insights. Integrations with the CRM and conferencing tools fail, so activity is not written back.

What to do about it

Check status.gong.io, which groups components under Foundation, Engage, Forecast, Enable and Data Cloud rather than naming every service individually. For any commercially important call happening during an incident, record it another way rather than trusting automatic capture, because a conversation that was not recorded cannot be recovered once the meeting ends.

Is it down for everyone, or just you?

If this page says Gong is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

SalesLoft
SalesLoft
ZoomInfo
ZoomInfo
Salesforce
Salesforce
HubSpot
HubSpot

Gong outage FAQ

Was my call recorded if Gong was down?
Not necessarily, and this is the failure that matters. Gong joins or ingests meetings automatically, and an incident during the call can mean nothing was captured. The meeting itself proceeds normally, so nobody notices at the time. For important calls during a known incident, a local recording or thorough notes are the only reliable backup.
Why do recent calls have no transcript or insights?
Recording, transcription and analysis happen in stages, and the later stages can lag well behind capture during and after an incident. A call that appears without a transcript has usually been recorded and is waiting to be processed. Give it time before reporting it missing; a genuinely missing call does not appear in the list at all.
Does a Gong outage affect my CRM data?
Gong writes activity back to the CRM, so during an incident that write does not happen and opportunities look quieter than they were. The CRM's own records are untouched. After recovery, some backfill occurs, but do not assume every call and email is reflected: check anything a forecast decision depends on.
Can I still take customer calls while Gong is down?
Yes. Gong observes conversations rather than carrying them, so your conferencing tool and phone system are unaffected and the meeting goes ahead normally. What you lose is capture, transcription and analysis. Nothing about the customer experience changes, which is precisely why the gap goes unnoticed until someone looks for the recording.
Is call data lost permanently during an outage?
Recordings already ingested are stored and return with the service. The permanent loss is limited to conversations that were never captured, because there is no source to reprocess. That asymmetry is worth knowing: historical data is safe, while the calls happening during the incident are the ones genuinely at risk.

How we measure this

  • We request Gong's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Gong publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Gong goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required