Dovetail Outage History

Started Oct 07, 2026, 06:00 PM UTC· resolved Oct 07, 2026, 07:33 PM UTC

1. investigating Oct 07, 2026, 06:00 PM UTC

   We're investigating an issue that's stopping new transcriptions from completing. Uploaded audio and video files may show a failed or stuck transcription.

2. resolved Oct 07, 2026, 07:33 PM UTC

   We are continuing to work on a fix for this incident.

Read the full incident report →

Started Sep 09, 2026, 06:00 AM UTC· resolved Sep 09, 2026, 09:22 AM UTC

1. investigating Sep 09, 2026, 06:00 AM UTC

   We are investigating reports that Chat and Agents are losing memory and stalling in some cases.

2. identified Sep 09, 2026, 07:06 AM UTC

   We have identified the root cause and we are rolling out a fix for this issue.

3. resolved Sep 09, 2026, 09:22 AM UTC

   The fix has been verified and the incident is now resolved.

Read the full incident report →

Started Aug 11, 2026, 04:00 PM UTC· resolved Aug 11, 2026, 06:38 PM UTC

1. investigating Aug 11, 2026, 04:00 PM UTC

   We're aware that some users are unable to connect or reconnect the Zapier integration, seeing an OAuth or authorization error. Our team is investigating and will post updates here as we learn more. This is impacting all customers using Zapier and Dovetail. If you're affected, no action is needed on your end right now — we'll update this page once we have a fix or workaround. We apologize for any inconvenience.

2. identified Aug 11, 2026, 06:15 PM UTC

   We've identified the root cause of the Zapier OAuth connection errors and are now working on a fix. We'll continue to post updates here as we make progress.

3. monitoring Aug 11, 2026, 06:32 PM UTC

   We implemented a fix and are currently monitoring the result.

4. resolved Aug 11, 2026, 06:38 PM UTC

   We've rolled back the change that caused the Zapier OAuth connection errors. If you were affected, please try the following steps: 1\. Do a hard refresh of your browser (or log out of Zapier and log back in). 2\. Try connecting your Zapier integration again. This should now work as expected. If you're still running into issues after these steps, please email [[email protected]](mailto:[email protected]) with a screen recording of the issue (with your browser console log open) so we can continue investigating.

Read the full incident report →

Started Aug 06, 2026, 10:00 PM UTC· resolved Aug 07, 2026, 08:00 AM UTC

1. investigating Aug 06, 2026, 10:00 PM UTC

   We are investigating an issue where using the **Copy to** or **Duplicate** actions within a project may incorrectly change the titles of the original data and the copied data to **"Loading"**. This issue is affecting customers across regions, and we are working to identify the cause and restore affected titles where possible. **Workaround:** At this time, we recommend avoiding the use of **Copy to** and **Duplicate** actions within projects until further notice. We will provide updates as more information becomes available..

2. identified Aug 06, 2026, 11:03 PM UTC

   We have identified the issue causing data titles to change to **“Loading”** when using the **Copy to** or **Duplicate** actions within a project. Our team is working on a fix to prevent this from happening going forward. We are also investigating the possibility of restoring affected data titles back to their original names. The title restoration process may take several hours, and we will provide another update once we have more information..

3. monitoring Aug 07, 2026, 03:56 AM UTC

   We have identified and fixed the root cause of this issue, so the **Copy to** and **Duplicate** actions will no longer change titles to "**Loading**". Our engineers are now working to restore the titles that were affected while the issue was active. You can now use the **Copy to** and **Duplicate** actions within project as normal. We will provide a further update once the restoration of affected titles is complete..

4. resolved Aug 07, 2026, 08:00 AM UTC

   This incident is now resolved. The Copy to and Duplicate actions are working normally and will no longer change titles to "Loading." Our engineers were able to restore the majority of affected titles, though a small number could not be recovered. If you notice any data still showing "Loading" as its title, you can safely rename it. We apologize for any inconvenience this may have caused, and thank you for your patience while we worked through this issue. If you continue to run into any issues, please reach out to our team at [email protected].

Read the full incident report →

Started Aug 06, 2026, 01:51 AM UTC· resolved Aug 06, 2026, 07:18 AM UTC

1. identified Aug 06, 2026, 01:51 AM UTC

   Following an update in Notion's MCP server, we have identified an issue causing chat and agents that use Notion MCP to fail. If you are encountering issues, please try disabling the Notion MCP connector while we resolve the issue. Thank you!

2. monitoring Aug 06, 2026, 05:54 AM UTC

   We have not observed any further errors related to the Notion MCP connector and are continuing to monitor closely. Chat and agents using Notion MCP should now be functioning normally.

3. resolved Aug 06, 2026, 07:18 AM UTC

   We have seen no further errors with the Notion MCP connector. This incident has been resolved.

Read the full incident report →

Started Jul 31, 2026, 06:40 AM UTC· resolved Aug 09, 2026, 11:41 PM UTC

1. identified Jul 31, 2026, 06:40 AM UTC

   We have identified higher than usual failure rates of citations appearing in Chat and Agent outputs. We are currently working on a fix. Thank you for your patience.

2. resolved Aug 03, 2026, 11:07 PM UTC

   This incident has been resolved. Citations should work as expected now. If you continue to run into any issues, please reach out to us at [[email protected]](mailto:[email protected])

3. identified Aug 04, 2026, 05:13 AM UTC

   We have identified that citation failure rates in Chat and Agent outputs have risen again. We are actively investigating this issue. Thank you for your patience.

Read the full incident report →

Started Jul 10, 2026, 05:26 AM UTC· resolved Jul 10, 2026, 12:31 PM UTC

1. investigating Jul 10, 2026, 05:26 AM UTC

   We're investigating an issue where some customers have reported that citations are no longer showing in some responses created by agents.

2. resolved Jul 10, 2026, 12:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2026, 04:49 AM UTC· resolved Jul 01, 2026, 07:06 AM UTC

1. investigating Jul 01, 2026, 04:49 AM UTC

   We are currently investigating this incident.

2. identified Jul 01, 2026, 06:27 AM UTC

   The root cause is identified and rolling out fix now.

3. monitoring Jul 01, 2026, 07:05 AM UTC

   We implemented a fix and are currently monitoring the result.

4. resolved Jul 01, 2026, 07:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 01:58 AM UTC· resolved Jun 30, 2026, 03:10 AM UTC

1. investigating Jun 30, 2026, 01:58 AM UTC

   We are currently investigating an issue where transcription is not working for customers using AWS as their transcription provider. If you are a workspace admin, you can check what transcription provider you're using by going to Workspace **(⋯) More → Settings → Transcription.** As a workaround, we recommend changing your transcription provider to **'Assembly AI'**. We'll provide an update as soon as we have more information.

2. monitoring Jun 30, 2026, 02:29 AM UTC

   We implemented a fix and are currently monitoring the result.

3. resolved Jun 30, 2026, 03:10 AM UTC

   This incident has been resolved. For any failed transcripts, please click "Retry" to re-generate the transcript. If you continue to run into any issues, please reach out to us at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Jun 30, 2026, 01:58 AM UTC· resolved Jun 30, 2026, 03:10 AM UTC

1. investigating Jun 30, 2026, 01:58 AM UTC

   We are currently investigating an issue where transcription is not working for customers using AWS as their transcription provider. If you are a workspace admin, you can check what transcription provider you're using by going to Workspace **(⋯) More → Settings → Transcription.** As a workaround, we recommend changing your transcription provider to **'Assembly AI'**. We'll provide an update as soon as we have more information..

2. monitoring Jun 30, 2026, 02:29 AM UTC

   We implemented a fix and are currently monitoring the result..

3. resolved Jun 30, 2026, 03:10 AM UTC

   This incident has been resolved. For any failed transcripts, please click "Retry" to re-generate the transcript. If you continue to run into any issues, please reach out to us at [[email protected]](mailto:[email protected])..

Read the full incident report →

Started Jun 25, 2026, 03:31 AM UTC· resolved Jun 26, 2026, 05:31 AM UTC

1. identified Jun 25, 2026, 03:31 AM UTC

   We're aware of an issue affecting speaker labels in Chat and Agents. We've temporarily disabled this feature while we work on a fix. During this time, Chat and Agents will not be able to answer questions about speaker information in transcripts.

2. resolved Jun 26, 2026, 05:31 AM UTC

   We've now resolved the issue with speaker labelling in Chat and Agents. We've fully restored this functionality and Chat and Agents are now fully operational.

Read the full incident report →

Started Jun 24, 2026, 11:04 PM UTC· resolved Jun 25, 2026, 01:52 AM UTC

1. identified Jun 24, 2026, 11:04 PM UTC

   Chat is currently unavailable for AU region workspaces. We've identified the cause and are working on a fix — we'll share updates here as we have them.

2. resolved Jun 25, 2026, 01:52 AM UTC

   This incident has been resolved. If you have an AU hosted workspace, we recommend performing a hard refresh of your browser before trying Chat again. If you continue to experience any issues, please reach out to us at [[email protected]](mailto:[email protected]).

Read the full incident report →

Started Jun 19, 2026, 04:00 PM UTC· resolved Jun 19, 2026, 07:31 PM UTC

1. investigating Jun 19, 2026, 04:00 PM UTC

   We are investigating an issue affecting customers globally where data and highlights are not appearing in **Table View** within projects. Users may see empty tables when viewing imported survey or project/highlights data in Table View. In some cases, if Table View is set as the default project view, it may appear as though project data has been lost. The underlying data remains intact and has not been deleted. **Current workaround:** Switch to an alternative project view (such as List or Board) to access and continue working with your data while we investigate. Our team has identified the issue and is actively working to determine the root cause and implement a fix. We will provide updates as more information becomes available..

2. resolved Jun 19, 2026, 07:31 PM UTC

   The issue affecting Table View within projects has now been resolved. Users should once again be able to view their data and highlights normally in Table View within projects. No customer data was lost as a result of this incident. If you were impacted, please refresh your browser (hard refresh recommended) before checking your projects: * **Mac:** Command + Shift + R * **Windows:** Ctrl + Shift + R If you continue to experience issues after refreshing, please contact our support team and provide a screenshot so they can continue investigating. Thank you for your patience while we investigated and resolved this issue..

Read the full incident report →

Started May 19, 2026, 06:09 AM UTC· resolved May 19, 2026, 07:04 AM UTC

1. investigating May 19, 2026, 06:09 AM UTC

   Some users are occasionally seeing errors when attempting to access pages in Dovetail or when sending requests to the Dovetail API. We are currently investigating this issue.

2. resolved May 19, 2026, 07:04 AM UTC

   We've implemented a fix and and are no longer seeing errors.

Read the full incident report →

Started May 10, 2026, 07:25 AM UTC· resolved May 10, 2026, 09:05 AM UTC

1. monitoring May 10, 2026, 07:25 AM UTC

   We have identified an issue with our service provider at 8:09 UTC and they have implemented a fix. continues to experience intermittent 504s / 500s. You may see the message "ERROR: Failed to contact the origin". We are working with the service provider to keep this incident updated, and we will send another update once the issue is fully resolved..

2. monitoring May 10, 2026, 08:56 AM UTC

   The service provider has implemented a fix, and we can see that the website is no longer experiencing issues. We are continuing to monitor the situation and will provide another update at 9:15 UTC..

3. resolved May 10, 2026, 09:05 AM UTC

   This incident has been resolved and our service provider is no longer experiencing any issues..

Read the full incident report →

Started Mar 19, 2026, 03:02 AM UTC· resolved Mar 19, 2026, 07:03 AM UTC

1. investigating Mar 19, 2026, 03:02 AM UTC

   We are currently investigating an incident that is impacting playback for redacted videos. Please note that this incident is only impacting users with **Viewer** role..

2. resolved Mar 19, 2026, 07:03 AM UTC

   This incident has been resolved. If you continue to run into this issue, please reach out to [[email protected]](mailto:[email protected]) so that we can have a look. Thanks for your patience..

Read the full incident report →

Started Mar 09, 2026, 01:55 AM UTC· resolved Mar 09, 2026, 04:52 AM UTC

1. investigating Mar 09, 2026, 01:55 AM UTC

   We are investigating an issue with AI docs **(beta)** and it is currently unavailable across all regions. As a workaround, users can generate a doc from chat..

2. resolved Mar 09, 2026, 04:52 AM UTC

   This issue has been resolved. Please refresh your page and try generating an AI doc again. Thank you for your patience! .

Read the full incident report →

Started Mar 02, 2026, 04:36 AM UTC· resolved Mar 02, 2026, 05:33 AM UTC

1. identified Mar 02, 2026, 04:36 AM UTC

   Contextual chat is currently down for workspaces with AI processing regions set to 'Australia'. Our team is currently working on a fix for this issue. Thank you for your patience with us..

2. resolved Mar 02, 2026, 05:33 AM UTC

   We have released a fix for this issue. Contextual Chat is now fully operational for all AU hosted workspaces. We appreciate your patience while we resolved this. If you continue to experience any issues, please contact our team at [**[email protected]**](mailto:[email protected]) so we can look into this again..

Read the full incident report →

Started Feb 26, 2026, 11:23 PM UTC· resolved Feb 27, 2026, 12:05 AM UTC

1. identified Feb 26, 2026, 11:23 PM UTC

   We’re currently investigating an issue affecting Ask Dovetail in Slack and Teams for customers who currently have multiple Slack or Teams connections set up to a single workspace. As a workaround, disconnect all existing connections and reconnect a single connection to Slack or Teams..

2. resolved Feb 27, 2026, 12:05 AM UTC

   We've diagnosed the issue and confirmed that the incident has not impacted any customer workspaces. Please reach out to [[email protected]](mailto:[email protected]) if you are finding any Ask Dovetail related issues in your workspace..

Read the full incident report →

Started Dec 09, 2025, 02:00 PM UTC· resolved Dec 09, 2025, 05:20 PM UTC

1. investigating Dec 09, 2025, 02:00 PM UTC

   Some users are currently unable to click and open data or insights within Dovetail. Clicking items directly in the UI doesn’t respond. **Workaround:** If available, users can still access content by opening the direct URL associated with the data. **Status:** Our team is currently investigating the issue. We’ll share updates here as we learn more..

2. investigating Dec 09, 2025, 03:31 PM UTC

   This issue currently affects only Board and Grid views. As a workaround, you can switch to a different data or insight view to access your content. We're still actively investigating. .

3. identified Dec 09, 2025, 04:58 PM UTC

   We have identified the issue, and the fix is on the way. We’ll provide another update as soon as it’s resolved..

4. resolved Dec 09, 2025, 05:20 PM UTC

   The issue has been resolved. To see the changes, you may need to hard refresh your browser. Thank you for your patience!.

Read the full incident report →

Started Dec 03, 2025, 08:30 PM UTC· resolved Dec 03, 2025, 11:52 PM UTC

1. investigating Dec 03, 2025, 08:30 PM UTC

   We’re currently investigating an issue where videos uploaded to Dovetail remain in a **“Processing, come back soon”** state. While transcripts and suggested highlights are completing normally, the video itself is unavailable. Our team is actively looking into this, and we’ll share an update as soon as we have more information. Thank you for your patience!.

2. identified Dec 03, 2025, 11:47 PM UTC

   We have found the root cause and are working on a fix. We appreciate your patience!.

3. resolved Dec 03, 2025, 11:52 PM UTC

   This incident has been resolved. If you continue to run into any issues, please reach out to us at [email protected]. .

Read the full incident report →

Started Dec 02, 2025, 10:35 PM UTC· resolved Dec 03, 2025, 02:21 AM UTC

1. investigating Dec 02, 2025, 10:35 PM UTC

   We are currently investigating two issues affecting the Browse page: 1. "All" filter not working — Selecting the _All_ filter displays all folders as empty, even when they contain projects. 2. Projects beyond the first 25 not loading — When viewing a folder with more than 25 projects, only the first 25 are visible and additional projects do not load. These issues may impact your ability to browse or locate projects. Our team is actively working on a fix and will provide updates as they become available. In the meantime, you can still find your projects using _Search_ or under _Your work_. .

2. resolved Dec 03, 2025, 12:14 AM UTC

   We have released a fix for this issue and it has now been resolved. We recommend performing a hard refresh of your browser (Cmd/ Ctrl + Shift + R) before accessing the Browse page again. If you are finding that the issue is still persisting, please get in touch with our team at [[email protected]](mailto:[email protected]).

3. monitoring Dec 03, 2025, 01:17 AM UTC

   We implemented a fix and are currently monitoring the result..

4. resolved Dec 03, 2025, 02:21 AM UTC

   This incident has been resolved..

Read the full incident report →

Started Nov 21, 2025, 03:30 PM UTC· resolved Nov 21, 2025, 06:02 PM UTC

1. investigating Nov 21, 2025, 03:30 PM UTC

   We’re currently investigating an issue where highlight exports fail to download. When attempting an export, users see the “Preparing download” toast briefly, but no follow-up toast appears, and no file is added to the browser’s download history. You can access your downloaded highlight by navigating to **Notifications**, where you’ll see “Your highlight is ready” along with a “Download” option. Please note: If you open Notifications and then close it, you won’t be able to reopen it unless a new notification comes in..

2. investigating Nov 21, 2025, 04:23 PM UTC

   We’re also seeing failures with the **Suggest Highlights** feature. Attempting to generate suggested highlights results in an **“Unexpected error occurred”** toast. Other Magic features may also be unavailable. **Workaround:** In _some_ cases, the highlights or actions appear after refreshing the browser..

3. resolved Nov 21, 2025, 06:02 PM UTC

   The issues affecting **highlight exports** and Magic features have been resolved. Users should now be able to download highlights and generate suggested highlights as expected. If you experienced problems during the incident: * Refresh your browser. * If your actions (exports or suggested highlights, etc) did not save, please try again. We apologize for the disruption and appreciate your patience while we resolved this issue..

Read the full incident report →

Started Nov 18, 2025, 03:22 AM UTC· resolved Nov 18, 2025, 05:19 AM UTC

1. investigating Nov 18, 2025, 03:22 AM UTC

   We are currently investigating an issue where chat and agents are unable to search for some data, including any data related to projects..

2. identified Nov 18, 2025, 03:51 AM UTC

   We've identified the root cause for this issue, and we are currently testing a fix..

3. monitoring Nov 18, 2025, 05:09 AM UTC

   We have released the fix and are now monitoring the result..

4. resolved Nov 18, 2025, 05:19 AM UTC

   We have released the fix and confirmed that functionality is now restored..

Read the full incident report →

Started Nov 17, 2025, 05:00 PM UTC· resolved Nov 17, 2025, 05:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →