Is Gong Down?

No — Gong is up

Gong's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 436 ms

Right now

The verdict is the worse of these two. How we decide

Gong's status page

status.gong.io · read 4 minutes ago · checked every 3 minutes

Operational

Gong's components, as its status page reports them
Component	Status
Data Capture	Operational
Web App	Operational
Mobile App	Operational
Engage	Operational
Forecast	Operational
Enable	Operational
Enrich	Operational
Data Cloud	Operational

Open their status page

FlareWarden checks

gong.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 436 ms
Checked: 19 minutes ago

By region

Ashburn reachable, 354 ms
Frankfurt reachable, 247 ms
Johannesburg reachable, 1210 ms
London reachable, 206 ms
Los Angeles reachable, 188 ms
Newark reachable, 217 ms
São Paulo reachable, 289 ms
Tokyo reachable, 783 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	140 ms	1 ms	10 ms	254 ms
Frankfurt	156 ms	2 ms	8 ms	226 ms
Johannesburg	249 ms	1 ms	6 ms	1177 ms
London	117 ms	3 ms	10 ms	191 ms
Los Angeles	91 ms	2 ms	12 ms	174 ms
Newark	120 ms	3 ms	12 ms	200 ms
São Paulo	57 ms	2 ms	8 ms	221 ms
Tokyo	180 ms	1 ms	7 ms	771 ms

We check that gong.io loads, not every feature behind it. Test it yourself

History

Incidents Gong reported

Since Oct 22, 15 days · from status.gong.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Gong website availability

Measured by FlareWarden · gong.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 362ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of gong.io from multiple regions every 6 hours. Gong's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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 the verdict is the worse of what it reports and what our checks see: a major outage of Gong itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Gong goes down

We check Gong every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required