Skip to main content
ZoomInfo logo

Is ZoomInfo Down?

No — ZoomInfo is up

Reachable from 6 of 8 checked regions — 2 regions answered but refused our checks

Average response time: 762ms

Last checked · checks run every 6 hours

Official status page: https://status.zoominfo.com

ZoomInfo uptime

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

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

77-day clean streak
Sep 13: 100.00% uptime, 22 checks
Sep 14: 100.00% uptime, 29 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 26 checks
Sep 17: 100.00% uptime, 18 checks
Sep 18: 100.00% uptime, 30 checks
Sep 19: 100.00% uptime, 31 checks
Sep 20: 100.00% uptime, 30 checks
Sep 21: 100.00% uptime, 23 checks
Sep 22: 100.00% uptime, 22 checks
Sep 23: 100.00% uptime, 29 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 20 checks
Sep 26: 100.00% uptime, 21 checks
Sep 27: 100.00% uptime, 26 checks
Sep 28: 100.00% uptime, 31 checks
Sep 29: 100.00% uptime, 29 checks
Sep 30: 100.00% uptime, 22 checks
Oct 1: 100.00% uptime, 22 checks
Oct 2: 100.00% uptime, 23 checks
Oct 3: 100.00% uptime, 21 checks
Oct 4: 100.00% uptime, 29 checks
Oct 5: 100.00% uptime, 31 checks
Oct 6: 100.00% uptime, 25 checks
Oct 7: 100.00% uptime, 21 checks
Oct 8: 100.00% uptime, 27 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 25 checks
Oct 11: 100.00% uptime, 21 checks
Oct 12: 100.00% uptime, 6 checks
Sep 13 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.

iad
423ms
DNS 14ms TCP 1ms TLS 12ms TTFB 416ms
jnb
HTTP 403 · challenge

Answered in 25ms — the origin is serving traffic, it just refused our client.

lax
546ms
DNS 70ms TCP 1ms TLS 12ms TTFB 524ms
lhr
724ms
DNS 106ms TCP 3ms TLS 12ms TTFB 683ms
nrt
HTTP 403 · challenge

Answered in 143ms — the origin is serving traffic, it just refused our client.

ord
1099ms
DNS 26ms TCP 1ms TLS 11ms TTFB 1091ms
sin
1192ms
DNS 9ms TCP 1ms TLS 14ms TTFB 1081ms
sjc
591ms
DNS 19ms TCP 3ms TLS 14ms TTFB 585ms

What ZoomInfo does

ZoomInfo sells B2B contact and company data, with tools for prospecting, enrichment and conversation intelligence layered on top. Sales teams build lists from it and pipe enriched records into a CRM automatically, so an outage stops prospecting and quietly leaves new CRM records missing the fields that route and score them.

What an outage looks like

Search returns no results or times out while the interface itself loads. Contact records open with fields blank rather than showing an error. Exports to CRM fail or complete with records missing enrichment. The browser extension stops surfacing data on LinkedIn and company sites. Enterprise API calls used for enrichment return errors, so downstream automation silently degrades.

What to do about it

Check status.zoominfo.com, which reports Sales, Marketing, Talent, Operations, the Enterprise API, Enrich, Engage and Chorus as separate products, so a broken enrichment job does not mean search is affected. Hold CRM imports until Enrich is healthy, because records written without enrichment look complete and are rarely revisited once they land.

Is it down for everyone, or just you?

If this page says ZoomInfo 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

ZoomInfo outage FAQ

Is ZoomInfo down or have I hit my credit limit?
Credit and export limits return an explicit message naming the limit, while an outage produces timeouts or empty results. Check status.zoominfo.com and the specific product you use, since Sales, Marketing and Talent are reported separately. If the platform is healthy and a colleague can export, the constraint is on your seat rather than the service.
Should I import records exported during an outage?
Check them first. Exports that complete during a degraded Enrich component can arrive with missing phone numbers, titles or firmographics, and those gaps are hard to spot in a large file. Records imported incomplete tend to stay incomplete, because nothing later prompts a re-enrichment. Re-running the export after recovery is usually cheaper than cleaning the CRM.
Does a ZoomInfo outage affect data already in my CRM?
No. Records already written to your CRM are yours and are unaffected by ZoomInfo being unreachable. What stops is new enrichment, refreshes of existing records, and any workflow that calls ZoomInfo as part of lead routing. Those workflows may fail silently rather than alerting, which is worth reviewing after an incident.
Why has the browser extension stopped showing contact data?
The extension queries ZoomInfo live for every profile you view, so it fails during an incident even though the page you are on loads normally. It usually shows nothing rather than an error. If the status page is clear, reinstalling or re-authenticating the extension is the next step, since its session can expire independently.
Do Chorus call recordings survive an outage?
Chorus is listed as its own component. Recordings already processed are stored and return with the service. Calls that took place while the component was degraded may not have been captured or transcribed at all, and there is no way to recover a conversation that was never recorded. Confirm capture for any critical call.

How we measure this

  • We request ZoomInfo's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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 ZoomInfo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ZoomInfo goes down

This page refreshes every 6 hours. 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