Aug <var data-var='date'> 7</var>, <var data-var='time'>13:31</var> UTC Resolved - Between 11:45 and 12:16 UTC, our transcription system was unavailable. During this window, meeting transcripts could temporarily not be viewed, and transcripts for newly recorded meetings were not processed. As a result, some meetings recorded on the morning of Aug 7 received their transcript and AI features (summaries, follow-up emails, insights, scorecards) with a delay. No data was lost. All meeting recordings were captured and stored normally throughout the incident. Affected meetings have since been processed, and all transcripts and AI follow-ups have been delivered. Timeline (UTC) - 11:45 A failed deployment left the transcription system in a faulty state; transcript viewing and processing began returning errors. - 11:46 Incident identified, investigation started. - 12:16 Fix deployed; transcript viewing and processing of new meetings restored. - Afternoon Meetings affected during the window were identified and reprocessed. All delayed transcripts and AI follow-ups delivered. What we're doing We've identified why the failed deployment wasn't rolled back cleanly and why affected meetings weren't retried automatically. We're adding automatic retries and monitoring so a short disruption like this can no longer delay transcripts without our systems catching up on their own.

Delayed meeting transcripts and AI follow-ups

Jan <var data-var='date'>27</var>, <var data-var='time'>14:34</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>27</var>, <var data-var='time'>12:28</var> UTC Monitoring - Our AI/LLM provider Microsoft Azure has a service issue at the moment. Updates are provided here: https://azure.status.microsoft/en-us/status. A subset of our AI chats might return "Something went wrong. Please try again." in the meantime. We'll monitor the situation and provide an update once resolved on Microsoft's side.

AI chat availability limited

Dec <var data-var='date'> 5</var>, <var data-var='time'>09:38</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'> 5</var>, <var data-var='time'>09:18</var> UTC Update - We are continuing to work on a fix for this issue. Dec <var data-var='date'> 5</var>, <var data-var='time'>09:05</var> UTC Identified - The HubSpot and Pipedrive APIs is currently not available due to a Cloudflare incident. Consequentially HubSpot and Pipedrive CRM syncs are not working in Demodesk. We're monitoring the situation and will inform you once the incident is resolved.

HubSpot, Pipedrive CRM sync delayed

Nov <var data-var='date'>18</var>, <var data-var='time'>18:04</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'>18</var>, <var data-var='time'>12:09</var> UTC Monitoring - It looks like the issue has been resolved. We'll continue to monitor. Nov <var data-var='date'>18</var>, <var data-var='time'>11:59</var> UTC Identified - Our CDN provider Cloudflare has an ongoing issue and some customers might not be able to connect to Demodesk at the moment. Cloudflare is tracking the incident here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 We're monitoring the situation and will provide updates as soon as possible.

CDN outage

Nov <var data-var='date'>11</var>, <var data-var='time'>08:37</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'>10</var>, <var data-var='time'>16:40</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Nov <var data-var='date'>10</var>, <var data-var='time'>16:40</var> UTC Investigating - Transcripts can currently take longer to process. We expect all pending transcripts to be processed by Tuesday (Nov 11th) morning (CET).

Increased recording processing times

Oct <var data-var='date'>21</var>, <var data-var='time'>10:14</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>17</var>, <var data-var='time'>13:56</var> UTC Identified - A Microsoft Azure Cloud issue is impacting processing times of recording summaries. The summaries will become available after the Microsoft issue gets resolved. No other functionalities have been impacted.

Microsoft Cloud issues delaying recording summary processing

Oct <var data-var='date'>16</var>, <var data-var='time'>07:56</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>15</var>, <var data-var='time'>10:25</var> UTC Update - We are continuing to work on a fix for this issue. Oct <var data-var='date'>15</var>, <var data-var='time'>10:24</var> UTC Identified - A Microsoft Azure Cloud issue is impacting processing times of recording summaries. The summaries will become available after the Microsoft issue gets resolved. No other functionalities have been impacted.

Jul <var data-var='date'> 9</var>, <var data-var='time'>08:00</var> UTC Resolved - A number of Demodesk meetings (both Meeting and Coaching&AI) experienced interruptions between 10am and 11am CEST today. Recordings of those meetings are available, however they may miss some moments during the interruption.

Interrupted Demodesk meetings

Feb <var data-var='date'> 7</var>, <var data-var='time'>08:00</var> UTC Resolved - Very few meetings that had the feature "GDPR compliant recording" enabled, faced a problem where participants could not submit the form to provide their consent. This was a UI defect that led a popup window to stay open after clicking "accept". Besides the misbehavior of the model, recordings did start correctly as soon as all participants gave their consent. The UI defect was fixed by rolling back the faulty changes.

GDPR compliant recording issues

Sep <var data-var='date'>21</var>, <var data-var='time'>16:09</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>21</var>, <var data-var='time'>14:40</var> UTC Identified - Google Calendar is having issues. Demodesk functionalities that read or write into Google Calendars might not work as expected. Google shares status updates and details on their status page here: https://www.google.com/appsstatus/dashboard/incidents/7uJZ5F1Uy4n1n74iMacQ

Google has an active incident for their Calendar API

Sep <var data-var='date'>13</var>, <var data-var='time'>08:00</var> UTC Resolved - For a period of a few minutes, Demodesk experienced significantly increased loading times across the whole application.

Increased loading time

May <var data-var='date'>23</var>, <var data-var='time'>16:00</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>23</var>, <var data-var='time'>12:20</var> UTC Monitoring - We have fixed the issue and are currently monitoring the systems. May <var data-var='date'>23</var>, <var data-var='time'>12:16</var> UTC Investigating - We currently have an incident that increases loading times on all Demodesk functionalities – we're investigating the cause.

Jun <var data-var='date'>21</var>, <var data-var='time'>08:24</var> UTC Resolved - Cloudflare resolved their incident and Demodesk is fully back to normal operation. Details on their outage can be found here: https://www.cloudflarestatus.com/incidents/xvs51y9qs9dj Jun <var data-var='date'>21</var>, <var data-var='time'>07:34</var> UTC Monitoring - We mitigated the major impact and the core functionality our system is restored. Since Cloudflare is widely spread we also see errors in our communication with third party integrations (eg. Hubspot). Jun <var data-var='date'>21</var>, <var data-var='time'>07:07</var> UTC Investigating - We see issues with various parts of the system. The root cause is an incident of Cloudflare (https://www.cloudflarestatus.com/).

Degraded system performance as our DNS and CDN Cloudflare is facing issues

Mar <var data-var='date'>18</var>, <var data-var='time'>15:30</var> UTC Resolved - Our API experienced high latencies which made it hard to use the application. Over a period of ~10 minutes, it was slow to us and for ~5 minutes most requests from the frontend timed out. We quickly identified the issue after the application was unresponsive and we were able to restore service within some minutes.

Slow and unresponsive application

Mar <var data-var='date'> 7</var>, <var data-var='time'>17:55</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 7</var>, <var data-var='time'>11:48</var> UTC Investigating - We are currently looking into increased meeting start times that affect a minority of meetings (<1%).

Increased meeting start times

Mar <var data-var='date'> 1</var>, <var data-var='time'>20:10</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 1</var>, <var data-var='time'>20:09</var> UTC Update - Audio/video is operation again and we're continuing to monitor the situation. Mar <var data-var='date'> 1</var>, <var data-var='time'>18:22</var> UTC Investigating - It's currently not possible to start meetings, as one of our service providers for audio/video communication has an outage. https://status.twilio.com/ We're working on a workaround and trying to resolve the situation as quickly as possible.

Twilio outage

Dec <var data-var='date'> 1</var>, <var data-var='time'>11:04</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'> 1</var>, <var data-var='time'>08:51</var> UTC Monitoring - A fix has been implemented and we consider the issue to be solved but keep monitoring the results. The expected impact is that CRM synchronization was delayed or even skipped in some rare cases. Dec <var data-var='date'> 1</var>, <var data-var='time'>07:48</var> UTC Identified - We identified an issue that causes certain functionality to be delayed (eg. syncing with CRMs). Demo starts should not be affected by this. We're working on resolving it.

Delays in parts of the system

Nov <var data-var='date'>22</var>, <var data-var='time'>18:10</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'>22</var>, <var data-var='time'>13:59</var> UTC Monitoring - Due to issue with a third party provider, we are experiencing delays in recordings as well as a minor subset of meetings starting times.

Delays in starting recordings and meetings

Nov <var data-var='date'> 5</var>, <var data-var='time'>16:35</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'> 4</var>, <var data-var='time'>11:40</var> UTC Update - We are continuing to monitor for any further issues. Nov <var data-var='date'> 4</var>, <var data-var='time'>11:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results Nov <var data-var='date'> 4</var>, <var data-var='time'>10:36</var> UTC Identified - We're experiencing disruptions related to the Google SSO functionality. The issue has been identified and a fix will be deployed and fully functional soon.

Google SSO login failures

Jun <var data-var='date'> 1</var>, <var data-var='time'>10:11</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 1</var>, <var data-var='time'>07:40</var> UTC Monitoring - DigitalOcean has fixed the issue, we're now going through all affected recordings to verify they're accessible. May <var data-var='date'>31</var>, <var data-var='time'>12:14</var> UTC Investigating - Our storage provider DigitalOcean has an outage, slowing down the availability of our recordings. We are working on a fix. (DigitalOcean ticket for reference: https://status.digitalocean.com/incidents/dw9913v02mq7)

Recordings not accessible

Mar <var data-var='date'>18</var>, <var data-var='time'>08:00</var> UTC Resolved - Microsoft Office is currently facing internal issues affecting your Demodesk scheduling and booking pages. We will update you immediately once it is resolved. Google Gsuite customers are not affected by this. You can hold meetings that are already scheduled.

Errors with booking for Microsoft Office users

Mar <var data-var='date'>17</var>, <var data-var='time'>17:00</var> UTC Resolved - Google Cloud reports increased network latencies, according to our monitoring the situation was resolved 17:20 UTC. Google status tracker for details: https://status.cloud.google.com/incident/cloud-networking/21006

Google Cloud partial network outage

Jan <var data-var='date'>11</var>, <var data-var='time'>18:10</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>11</var>, <var data-var='time'>16:10</var> UTC Identified - One of our storage cloud providers is having an issue with serving files. This means that viewing recordings of past meetings might not be possible currently. The recordings of running demos are not affected.

Some recordings are currently unaccessible

Jan <var data-var='date'> 2</var>, <var data-var='time'>15:48</var> UTC Completed - The storage migration of our image assets has been completed successfully and without downtime. Jan <var data-var='date'> 2</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>25</var>, <var data-var='time'>12:03</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time. Playbook previews may not show as expected.

Playbook previews update

Nov <var data-var='date'>26</var>, <var data-var='time'>11:29</var> UTC Resolved - This incident has been resolved and we identified specific ways to prevent this from happening again which will be implemented. Nov <var data-var='date'>26</var>, <var data-var='time'>11:16</var> UTC Monitoring - We identified issues in our networking configuration and were able to fix the issues. We're currently monitoring the configuration change and identify the next steps to prevent this error in the future. Nov <var data-var='date'>26</var>, <var data-var='time'>09:05</var> UTC Investigating - We are currently investigating this issue.

Is Demodesk down?

Demodesk status is UP

Lastest published events

Delayed meeting transcripts and AI follow-ups

AI chat availability limited

HubSpot, Pipedrive CRM sync delayed

Demodesk Services, Components and Regions

Recent Demodesk events

Delayed meeting transcripts and AI follow-ups

AI chat availability limited

HubSpot, Pipedrive CRM sync delayed

CDN outage

Increased recording processing times

Microsoft Cloud issues delaying recording summary processing