CloudTalk Outage History

CloudTalk is up right now

CloudTalk had 28 outages in the last 2 years totaling 350h 22m of downtime — averaging 1.2 incidents per month.

There were 28 CloudTalk outages since August 14, 2025 totaling 350h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cloudtalk.io

Minor June 29, 2026

Degraded performance and elevated calling errors

Detected by Pingoru
Jun 29, 2026, 04:03 PM UTC
Resolved
Jun 29, 2026, 04:03 PM UTC
Duration
—
Affected: Mobile ApplicationDesktop ApplicationOutbound calls
Timeline · 2 updates
  1. identified Jun 29, 2026, 04:00 PM UTC

    Status: Identified We're experiencing an elevated level of calling errors and are currently looking into the issue. We are reverting faulty deployments of our services. Affected components Desktop Application (Partial outage) Outbound calls (Partial outage) Outbound calls (Partial outage) Outbound calls (Partial outage) Mobile Application (Partial outage) Outbound calls (Partial outage)

  2. resolved Jun 29, 2026, 04:03 PM UTC

    Status: Resolved Issue has been fixed. Affected components Mobile Application (Operational) Outbound calls (Operational) Desktop Application (Operational) Outbound calls (Operational) Outbound calls (Operational) Outbound calls (Operational)

Read the full incident report →

Minor June 18, 2026

Partial System Outage

Detected by Pingoru
Jun 18, 2026, 04:16 PM UTC
Resolved
Jun 18, 2026, 04:16 PM UTC
Duration
—
Affected: Mobile ApplicationAnalyticsCall recordingCloudTalk DialerIntegrationsDesktop ApplicationCloudTalk DashboardMessagingVoiceAgentsOutbound callsOutbound callsInbound calls
Timeline · 5 updates

Read the full incident report →

Minor June 8, 2026

Campaigns loading issues

Detected by Pingoru
Jun 08, 2026, 08:36 AM UTC
Resolved
Jun 08, 2026, 08:36 AM UTC
Duration
—
Affected: CloudTalk Dialer
Timeline · 2 updates
  1. identified Jun 08, 2026, 08:26 AM UTC

    Status: Identified We are investigating an issue causing some campaigns to fail to load in the Dashboard. Affected users may see an incomplete or empty campaign list. Our investigation has identified a database schema inconsistency between environments that can cause campaign-related requests to fail under certain conditions. We have prepared a fix and are currently deploying it to production. Affected components CloudTalk Dialer (Degraded performance)

  2. resolved Jun 08, 2026, 08:36 AM UTC

    Status: Resolved We have applied a fix, we are monitoring the situation. Affected components CloudTalk Dialer (Operational)

Read the full incident report →

Minor April 27, 2026

Outage of outbound calls to Czech mobile and landline numbers

Detected by Pingoru
Apr 27, 2026, 10:47 AM UTC
Resolved
Apr 27, 2026, 10:47 AM UTC
Duration
—
Affected: Outbound callsOutbound calls
Timeline · 3 updates
  1. investigating Apr 27, 2026, 08:07 AM UTC

    Status: Investigating We are currently experiencing an outage affecting outbound VoIP calls to Czech Republic phone numbers (prefix +420). Customers attempting to dial these destinations may encounter immediate call drops or error messages. Affected components Outbound calls (Partial outage)

  2. identified Apr 27, 2026, 08:10 AM UTC

    Status: Identified Our engineering team has completed their initial diagnostics and confirmed that our internal VoIP infrastructure and network are functioning normally. We have successfully isolated the root cause of the outage to an upstream international carrier partner responsible for routing outbound traffic to the Czech Republic. The carrier is currently experiencing network instability on their end, which is preventing these calls from completing. Affected components Outbound calls (Partial outage)

  3. resolved Apr 27, 2026, 10:47 AM UTC

    Status: Resolved Issue has been fully resolved. Affected components Outbound calls (Operational)

Read the full incident report →

Minor April 9, 2026

Call Processing Delays

Detected by Pingoru
Apr 09, 2026, 05:29 PM UTC
Resolved
Apr 09, 2026, 05:29 PM UTC
Duration
—
Affected: Call recording
Timeline · 3 updates
  1. investigating Apr 09, 2026, 01:20 PM UTC

    Status: Investigating We are currently experiencing an issue affecting call processing. This may result in delayed availability of call recordings and delayed dial tone on outbound calls. Our team is investigating and working to restore normal service as quickly as possible. Affected components Call recording (Degraded performance)

  2. monitoring Apr 09, 2026, 04:27 PM UTC

    Status: Monitoring The root cause of the incident has been identified, and steps have been taken to resolve the issue. Affected components Call recording (Operational)

  3. resolved Apr 09, 2026, 05:29 PM UTC

    Status: Resolved The incident has been resolved. Full functionality has been restored. Affected components Call recording (Operational)

Read the full incident report →

Minor April 1, 2026

Issues with inbound calls outside EU region

Detected by Pingoru
Apr 01, 2026, 11:39 AM UTC
Resolved
Apr 01, 2026, 11:39 AM UTC
Duration
—
Affected: Inbound calls
Timeline · 3 updates
  1. identified Apr 01, 2026, 08:26 AM UTC

    Status: Identified We have identified an infrastructure issue currently impacting inbound call connectivity for regions outside of Europe. As a result, some users may face issues with incoming calls. We apologize for the interruption and will provide a further update as soon as the issue is resolved. Affected components Inbound calls (Degraded performance) Inbound calls (Degraded performance) Inbound calls (Degraded performance)

  2. monitoring Apr 01, 2026, 08:52 AM UTC

    Status: Monitoring We have successfully resolved the infrastructure issue that was impacting inbound call connectivity for regions outside of Europe. Service is now operating normally across all affected areas. Our team will continue to monitor the situation closely to ensure continued stability. Affected components Inbound calls (Operational) Inbound calls (Operational) Inbound calls (Operational)

  3. resolved Apr 01, 2026, 11:39 AM UTC

    Status: Resolved Service is operating normally across all areas. Affected components Inbound calls (Operational) Inbound calls (Operational) Inbound calls (Operational)

Read the full incident report →

Minor February 25, 2026

Delayed call processing

Detected by Pingoru
Feb 25, 2026, 04:35 PM UTC
Resolved
Feb 25, 2026, 04:35 PM UTC
Duration
—
Affected: Analytics
Timeline · 2 updates
  1. investigating Feb 25, 2026, 04:00 PM UTC

    Status: Investigating We are facing issues with calls and call history. Call history is not showing recent calls. Calls will appear with some delay. We are working on fixing the problem and synchronizing delayed data. Affected components Analytics (Degraded performance)

  2. resolved Feb 25, 2026, 04:35 PM UTC

    Status: Resolved The situation is resolved, our systems have caught up with synchronizing delayed data. Affected components Analytics (Operational)

Read the full incident report →