Demodesk Outage History

Demodesk is up right now

Pingoru has recorded 30 incidents for Demodesk: 5 in the last 12 months and 1 in the last 90 days.

Source: status.demodesk.com

30incidents recorded
5last 12 months
1last 90 days
5 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Demodesk in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 527 (0%)

Incidents, newest first

Minor August 7, 2026 Delayed meeting transcripts and AI follow-ups 31m

Started Aug 07, 2026, 11:45 AM UTC· resolved Aug 07, 2026, 12:16 PM UTC

  1. resolved Aug 07, 2026, 01:31 PM UTC

    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.

Read the full incident report →

Minor January 27, 2026 AI chat availability limited 2h 6m AI / LLM

Started Jan 27, 2026, 12:28 PM UTC· resolved Jan 27, 2026, 02:34 PM UTC

  1. monitoring Jan 27, 2026, 12:28 PM UTC

    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.

  2. resolved Jan 27, 2026, 02:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 5, 2025 HubSpot, Pipedrive CRM sync delayed 32m HubSpot HubSpot APIs

Started Dec 05, 2025, 09:05 AM UTC· resolved Dec 05, 2025, 09:38 AM UTC

  1. identified Dec 05, 2025, 09:05 AM UTC

    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.

  2. identified Dec 05, 2025, 09:18 AM UTC

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

  3. resolved Dec 05, 2025, 09:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 CDN outage 6h 5m

Started Nov 18, 2025, 11:59 AM UTC· resolved Nov 18, 2025, 06:04 PM UTC

  1. identified Nov 18, 2025, 11:59 AM UTC

    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.

  2. monitoring Nov 18, 2025, 12:09 PM UTC

    It looks like the issue has been resolved. We'll continue to monitor.

  3. resolved Nov 18, 2025, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 10, 2025 Increased recording processing times 15h 57m Transcriptions

Started Nov 10, 2025, 04:40 PM UTC· resolved Nov 11, 2025, 08:37 AM UTC

  1. investigating Nov 10, 2025, 04:40 PM UTC

    Transcripts can currently take longer to process. We expect all pending transcripts to be processed by Tuesday (Nov 11th) morning (CET).

  2. monitoring Nov 10, 2025, 04:40 PM UTC

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

  3. resolved Nov 11, 2025, 08:37 AM UTC

    This incident has been resolved.

Read the full incident report →