Zoominfo driftsforstyrrelser

1. 4. september 2026 kl. 19.15 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker GMM Studio Audiences. Vores ingeniørteam arbejder aktivt på dette, og vi vil levere en opdatering inden længe.

2. 4. september 2026 kl. 20.16 UTCinvestigating

   Vores ingeniørhold fortsætter med at undersøge problemet, der påvirker GMM Studio Audiences. Vi vil sende yderligere opdateringer her som vi har dem.

3. 4. september 2026 kl. 20.34 UTCmonitoring

   Vi har identificeret problemet påvirker GTM Studio Audiences og har gennemført en rettelse. Vores team overvåger i øjeblikket nøje resultaterne, og på nuværende tidspunkt bør GMM Studio Audience-tjenester genoprettes.

4. 4. september 2026 kl. 20.48 UTCresolved

   Denne hændelse påvirker GTM Studio Audiences er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 17.13 UTCmonitoring

   I tidsrammen 10: 45 til 12: 40 ET en delmængde af opkald kan ikke være blevet registreret. Vores ingeniør har løst dette, og opkald efter 12: 40 pm ET vil blive registreret som forventet. Desuden kan du se forsinkelser i opkald behandling gennem slutningen af dagen. Hvis dit møde blev optaget gennem din video konference udbyders cloud optagelse, kan du manuelt importere optagelsen fil i Chorus platform. Instruktioner til dette fundet her: https: / / help.zoominfo.com / s / article / How- to- Import- a- Recording- Into- Chorus I løbet af den ramte tid, nogle brugere fejlagtigt modtaget en e-mail-meddelelse om, at deres kalender integration blev afbrudt. Din kalenderforbindelse forbliver aktiv og operationel; der er ikke behov for handling fra din side. Hvis du ønsker at verificere eller gentilslutte din kalender, skal du følge de trin, der er skitseret her: https: / / help.zoominfo.com / s / article / How- to- Connect- and- Sync- Your- Calendar

2. 2. september 2026 kl. 20.55 UTCresolved

   Denne hændelse er blevet løst, men du kan se forsinkelser i opkald behandling gennem slutningen af dagen.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 4. august 2026 kl. 19.29 UTCinvestigating

   We are aware of and currently investigating an issue causing processing issues on large list processing including CSV Exports, ListMatch, Audience creation. During this time you may see processing delays/failures when processing large lists/exports within the ZoomInfo Platforms. We will continue to post updates as we have them.

2. 4. august 2026 kl. 19.41 UTCidentified

   We've identified this List processing issue is due to an issue one of our third party vendors is experiencing. We are both working with our vendor for updates and investigating mitigation strategies on our end where possible. We expect Jobs that experience issues will be queued for retry once the issue is resolved.

3. 4. august 2026 kl. 20.59 UTCidentified

   We are continuing to work with our vendor while still exploring mitigation strategies on our end. We will continue to post updates as we have them. We appreciate your patience and understanding as we explore solutions and work with our vendor.

4. 4. august 2026 kl. 23.06 UTCmonitoring

   We have implemented mitigation steps on our end and are currently monitoring the results. Though we don't expect to see many failed jobs, If you do see a failed message please retry that export/list.

5. 4. august 2026 kl. 23.19 UTCresolved

   This issue has been resolved. Though we don't expect to see many failed jobs, If you do see a failed message please retry that export/list.

1. 28. juli 2026 kl. 11.43 UTCinvestigating

   Chorus oplever i øjeblikket betydelig latency, hvilket kan forhindre brugerne i at få adgang til eller navigere platformen. Bemærk: Opkaldssammenføjning og optagelse funktionalitet forbliver operationelle. Vores Engineering team er aktivt undersøge problemet og arbejder på at genoprette normal platform ydeevne.

2. 28. juli 2026 kl. 12.06 UTCinvestigating

   Problemet med Chorus platforms ydeevne er løst. Vores ingeniørhold har genoprettet normal platformspræstation, og Chorus fungerer nu som forventet.

3. 28. juli 2026 kl. 12.07 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 08.14 UTCinvestigating

   Vi er opmærksomme på og undersøger et problem, der påvirker Intent Search i ZoomInfo platformen. Kunderne kan opleve fejl eller manglende lydhørhed, når de udfører søgninger, der er afhængige af Intent data. Vores ingeniørhold er flittigt undersøge problemet og arbejder på at genoprette normal service så hurtigt som muligt.

2. 24. juli 2026 kl. 08.19 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 24. juli 2026 kl. 08.27 UTCresolved

   Spørgsmålet om Intent Search er blevet løst. Vores ingeniørhold har implementeret et fix, og platformen fungerer nu som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juli 2026 kl. 15.55 UTCresolved

   Under tidsrammen for 20 juli 7 am ET til 21 juli 10 am ET en delmængde af indspillede opkald kan ikke have fanget video komponent. Vores Engineering team udgivet et fix for dette, og opkald efter 10 am ET den 21. juli vil optage video som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 17.02 UTCinvestigating

   Vi oplever i øjeblikket problemer med en tredjeparts leverandør, der påvirker alle Chorus tjenester. I løbet af denne tid, anbefaler vi, at klienter udnytte indfødte Zoom Recording hvis tilgængelig. Vi er aktivt at overvåge situationen med denne leverandør, samt undersøgelsesmuligheder på vores ende for at hjælpe afbøde, og vil give opdateringer som vi modtager dem.

2. 10. juli 2026 kl. 18.01 UTCmonitoring

   Chorus Services er blevet genoprettet, og vores ingeniørhold vil fortsat overvåge resultaterne. Vores Engineering team vil manuelt ombehandle alle opkald, der blev hængende behandling på grund af tredjeparts leverandør afbrydelse.

3. 10. juli 2026 kl. 18.26 UTCresolved

   Den hændelse, der påvirker Chorus tjenester er blevet løst. Vores ingeniørhold vil fortsætte oparbejdningen af alle opkald i behandling.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 10.20 UTCinvestigating

   Vi oplever i øjeblikket problemer med backend behandling af publikum. Holdet arbejder flittigt på at løse problemet.

2. 10. juli 2026 kl. 11.18 UTCmonitoring

   Vores ingeniørhold har løst problemet, der påvirker slutbehandlingen af publikum. Tjenesten er blevet genoprettet, og publikumsbehandlingen er genoptaget. Vores team vil fortsætte med at overvåge tjenesten, mens den resterende behandling backlog rydder.

3. 10. juli 2026 kl. 12.20 UTCresolved

   Alle tjenester fungerer nu normalt, og publikumsbehandling er vendt tilbage til normal drift.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 06.32 UTCidentified

   Vi er opmærksomme på og undersøger spørgsmål, der berører RingLead-platformen. Kunderne kan opleve intermitterende serviceforstyrrelser, herunder timeout, forringet ydeevne eller svært ved at få adgang til RingLead-funktioner. Vores Engineering team er aktivt undersøge problemet og arbejder på at genoprette normal service så hurtigt som muligt.

2. 10. juli 2026 kl. 06.40 UTCmonitoring

   Vores ingeniørhold har identificeret og løst problemet, der påvirker RingLead platformen. Vi fortsætter med at overvåge platformen nøje for at sikre, at tjenesterne forbliver stabile. Brugerne bør nu kunne få adgang til og bruge RingLead som forventet.

3. 10. juli 2026 kl. 06.45 UTCresolved

   Vores ingeniørhold har løst problemet, der påvirker RingLead platformen. Tjenester er blevet genoprettet, og brugerne bør nu kunne få adgang til og bruge RingLead som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 20.46 UTCinvestigating

   Vores Engineering team er i øjeblikket klar over og undersøge et problem påvirker e-mail verifikation på både Neverbounce API og standalone platform. I løbet af denne tid, kan brugerne opleve latency eller en højere frekvens af ubekendte eller invalider, når du kontrollerer e-mails. Tak for Deres tålmodighed, mens vi arbejder på at løse dette problem. Vi vil levere opdateringer, som vi har dem.

2. 9. juli 2026 kl. 21.40 UTCmonitoring

   Vores ingeniørhold har implementeret en rettelse og overvåger i øjeblikket resultaterne. Vi arbejder også på at omarbejde alle udestående job, som måtte være blevet påvirket af latenstiden.

3. 9. juli 2026 kl. 23.11 UTCresolved

   Spørgsmålet, der forårsager øget latency for e-mail-verifikation er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 11.21 UTCinvestigating

   Vi er opmærksomme på og undersøger spørgsmål, der berører RingLead-platformen. Kunderne kan opleve intermitterende serviceforstyrrelser, herunder timeout, forringet ydeevne eller svært ved at få adgang til RingLead-funktioner. Vores Engineering team er aktivt undersøge problemet og arbejder på at genoprette normal service så hurtigt som muligt.

2. 1. juli 2026 kl. 12.07 UTCmonitoring

   Vores ingeniørhold har identificeret og løst problemet, der påvirker RingLead platformen. Vi fortsætter med at overvåge platformen nøje for at sikre, at tjenesterne forbliver stabile. Brugerne bør nu kunne få adgang til og bruge RingLead som forventet.

3. 1. juli 2026 kl. 15.19 UTCresolved

   Vores ingeniørhold har løst problemet, der påvirker RingLead platformen. Tjenester er blevet genoprettet, og brugerne bør nu kunne få adgang til og bruge RingLead som forventet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 09.20 UTCidentified

   We have identified an issue impacting certain Search and Intent-related services. As part of our mitigation efforts, some scheduled workflows, CSV exports, and background processing jobs have been temporarily delayed. Our Engineering team has identified the root cause and is actively working toward a full resolution. Users may experience delays in search-related processing, workflow execution, and CSV export operations. We will continue to provide updates as more information becomes available.

2. 22. juni 2026 kl. 10.08 UTCresolved

   The issue impacting Enrich, Intent, CSV exports, and workflow processing has been resolved. Users should now be able to run enrichments, list uploads, CSV exports, and workflows as expected. Our Engineering team has fixed the issue.

1. 18. juni 2026 kl. 09.00 UTCinvestigating

   We are aware of and currently investigating an issue impacting users' ability to log in to Chorus. Users may see the Chorus page stuck on the loading screen or may be unable to access the Chorus platform. Our engineering teams are actively investigating and working to restore access as soon as possible. We will provide updates as more information becomes available.

2. 18. juni 2026 kl. 09.50 UTCresolved

   The issue impacting Chorus login and platform access has been resolved. Users should now be able to successfully access Chorus and utilize platform functionality as expected. Our engineering teams have implemented a fix and confirmed service restoration.

1. 17. juni 2026 kl. 19.36 UTCinvestigating

   We are aware of issues impacting Chorus login, call recording, and email/calendar sync. During this time, calls may not be recorded and newly scheduled calls may not sync from your calendar. Additionally, users may see an error when attempting to login to the Chorus platform. Our Engineering team is actively investigating this issue and is working to resolve it as soon as possible.

2. 17. juni 2026 kl. 19.59 UTCmonitoring

   Our Engineering team has implemented a fix and is now monitoring it. At this time, Chorus login, call recording, and email/calendar sync functionality should be fully restored. If your meeting was recorded through your video conference provider’s cloud recording, you can manually import the recording file into the Chorus platform. Instructions for this found here: https://help.zoominfo.com/s/article/How-to-Import-a-Recording-Into-Chorus

3. 17. juni 2026 kl. 20.09 UTCresolved

   The Chorus issues have been resolved. If your meeting was recorded through your video conference provider’s cloud recording, you can manually import the recording file into the Chorus platform. Instructions for this found here: https://help.zoominfo.com/s/article/How-to-Import-a-Recording-Into-Chorus

1. 2. juni 2026 kl. 16.20 UTCinvestigating

   Our Engineering team is currently aware of and investigating an issue impacting jobs from processing as expected on both Neverbounce API and the standalone platform. During this time, users may have issues uploading lists, and lists may take longer to process than expected. Our Engineering team is working as quickly as possible to restore functionality. Thank you for your patience as we work to resolve this issue.

2. 2. juni 2026 kl. 17.54 UTCmonitoring

   Our Engineering team has identified the issue and implemented a fix. Any new jobs should now process as expected on both the Neverbounce platform and Neverbounce API. Any jobs that did not process as expected during this incident should begin to process over the next couple of hours. Thank you for your patience as our team works to resolve this issue. We will continue to monitor and will share an update when all jobs have been processed as expected.

3. 2. juni 2026 kl. 20.58 UTCresolved

   Our Engineering team has confirmed that all previously submitted jobs have processed successfully on Neverbounce API and the Neverbounce platform. Jobs, such as list uploads and verification, should process as expected moving forward.

1. 1. juni 2026 kl. 15.11 UTCinvestigating

   We are aware of and investigating an issue causing the ZoomInfo Chrome Extension to endlessly load and eventually fail with an error for some users. Please know our Engineering teams are working hard to resolve these issues and get everything up and running as soon as possible.

2. 1. juni 2026 kl. 15.56 UTCmonitoring

   Our Engineering team implemented a fix for this issue and the Chrome Extension should now be functioning as expected. Users may need to perform a hard refresh of their browser for the extension to load, CMD+Shift+R for Macs and Ctrl+Shift+R for PCs. We are continuing to monitor to ensure the issue is fully resolved.

3. 1. juni 2026 kl. 16.06 UTCresolved

   This incident has been resolved.

1. 28. april 2026 kl. 14.21 UTCidentified

   We are aware some calls recorded Monday April, 27th are not displaying the video after the call has processed. Our Engineering team is working to resolve this so videos appear for all impacted calls currently not displaying the video. In the meantime, audio and transcripts should still be available.

2. 28. april 2026 kl. 20.12 UTCmonitoring

   Engineering has released a fix for the impacted calls and video should now be fully restored for calls on Monday April, 27th. We will also be reprocessing impacted calls to ensure the transcript, speaker separation, and meeting summaries are available.

3. 29. april 2026 kl. 03.48 UTCresolved

   This incident has been resolved and all calls have been re-processed.

1. 21. april 2026 kl. 14.46 UTCinvestigating

   We are aware of and investigating an issue that may cause latency or errors when creating and enriching an Audience. In addition you may see an error or freezing when attempting to open Audiences. Please know our engineering teams are working hard to resolve these issues and get everything up and running as soon as possible.

2. 21. april 2026 kl. 17.59 UTCinvestigating

   We are continuing to investigate the issue impacting Audiences within GTM Studio, users may be experiencing latency when creating or enriching Audiences. Our Engineering teams are actively working to identify the root cause and resolve this issue as quickly as possible. We will provide updates as new information becomes available.

3. 21. april 2026 kl. 19.14 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 21. april 2026 kl. 19.26 UTCresolved

   This incident has been resolved.

1. 20. april 2026 kl. 15.19 UTCinvestigating

   We are aware of an issue impacting users' ability to run enrichment, refresh, and initial ingestion for audiences in GTM Studio.  Our Engineering teams are actively investigating the issue.

2. 20. april 2026 kl. 15.20 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. april 2026 kl. 15.23 UTCinvestigating

   We are aware of an issue impacting users' ability to run enrichment, refresh, and initial ingestion for audiences in GTM Studio.  The issue appears related to a third party vendor and our Engineering teams are actively investigating and escalating the issue.

4. 20. april 2026 kl. 18.40 UTCmonitoring

   Our third-party vendor has implemented a fix, and the issue with running enrichment, refresh, and initial ingestion for audiences in GTM Studio should now be resolved. We will continue to monitor results and updates with our third-party vendor to ensure no additional issues are identified.

5. 20. april 2026 kl. 19.27 UTCresolved

   Our third-party vendor has implemented a fix and services are fully restored.

1. 13. april 2026 kl. 19.14 UTCinvestigating

   We are aware of and investigating an issue causing the ZoomInfo Chrome Extension to appear blank for some users. Please know our Engineering teams are working hard to resolve these issues and get everything up and running as soon as possible.

2. 14. april 2026 kl. 20.25 UTCidentified

   We have identified that a recent Chrome update is causing the ZoomInfo extension to appear blank for some users. We are actively monitoring the status of a fix with Chromium and will provide updates as we receive them.

3. 16. april 2026 kl. 15.02 UTCresolved

   Chrome has released a fix in their latest available version of 147.0.7727.101, which resolves the ZoomInfo Chrome extension appearing blank for users. All users will need to update their Chrome to version 147.0.7727.101 or later in order for the ZoomInfo Chrome extension issue to be fully resolved. Instructions for updating your Chrome: 1. In Google Chrome, click the three-dot menu (⋮) in the top-right corner 2. Hover over Help and select About Google Chrome 3. Chrome will display your current version and automatically download any available updates 4. Once the download is complete, click Relaunch to apply the update If you do not see an update available or are still on a lower version than the fixed version, you may need to work with your internal IT/help desk team to request the update.