ZoomInfo Outage History

ZoomInfo's Chorus service experienced a video processing issue where calls recorded on Monday, April 27th failed to display video content after processing, though audio and transcripts remained available. The engineering team identified the problem, deployed a fix to restore video functionality, and reprocessed all affected calls to ensure complete restoration of video, transcripts, speaker separation, and meeting summaries. The incident was fully resolved after 13.5 hours with all impacted calls successfully reprocessed.

ZoomInfo's GTM Studio experienced platform latency issues affecting Audience functionality, causing users to encounter delays, errors, and freezing when creating, enriching, or opening Audiences. The engineering team investigated the root cause and implemented a fix after 4.8 hours, with monitoring in place to ensure resolution.

ZoomInfo experienced a 4.1-hour outage affecting GTM Studio Audiences, preventing users from running enrichment, refresh, and initial ingestion operations for their audiences. The issue was traced to a third-party vendor problem that ZoomInfo's engineering teams escalated for resolution. The vendor implemented a fix that fully restored all GTM Studio Audiences functionality.

The ZoomInfo Chrome Extension appeared blank for some users due to a recent Chrome browser update. The issue affected the ZoomInfo Powered by DiscoverOrg component for 67.9 hours. The problem was resolved when Chrome released version 147.0.7727.101, requiring users to update their browser to this version or later to restore full extension functionality.

ZoomInfo's Chorus service experienced call recording issues for customers using Zoom streaming, lasting 4.6 hours. During the outage, the service automatically fell back to bot-based recording where possible, and users were advised to use Zoom's cloud recording with manual import as an alternative. The issue was resolved with all Zoom streaming calls confirmed to be recording properly via the notetaker bot.

ZoomInfo's Chorus call recording service experienced a major outage for 25 minutes, preventing calls from being recorded or causing processing delays. The engineering team investigated and resolved the issue while recommending users temporarily record calls through their video conference providers and manually import them into Chorus. The service was restored after active investigation and remediation efforts.

ZoomInfo's SalesOS platform experienced issues where the homepage appeared blank and signals failed to display correctly on company profile pages. The incident affected the core ZoomInfo platform functionality for 42 minutes. Engineering teams implemented and monitored a fix, restoring normal access to the homepage and signals display.

ZoomInfo's Chorus platform experienced login issues that prevented customers from accessing the service and caused calls to either not be recorded or experience processing delays. The engineering team implemented a fix after 51 minutes, fully restoring login and call recording functionality. Customers were advised to use their video conference provider's cloud recording as a workaround and could manually import those recordings once access was restored.

ZoomInfo experienced a 2.8-hour service disruption affecting Chorus functionality, including CoPilot features, email synchronization, and delayed processing of call recordings (though recordings continued to be captured). The engineering team worked with their vendor to implement a fix that fully restored call processing and email sync. The incident was resolved with systems returning to normal operation while the team monitored for potential data loss.

ZoomInfo experienced a 38-minute incident where users encountered latency and errors when accessing contact data, with information failing to load properly across multiple platform areas and contact exports being unavailable. Users reported that client information was not displaying as expected during the outage. Engineering implemented a fix that restored normal contact data functionality and resolved the issue.