CloudTalk Outage History

21 incidents recorded over the last 365 days, 21 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded CloudTalk Incident

CloudTalk incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 13, 2026Something is not working correctlyThe issues at ElevenLabs, one of our AI providers, are resolved. All VoiceAgent functionality is stable again.3h 32mResolved
Aug 28, 2026Scheduled database upgrade of contactsMaintenance has started107h 53mResolved
Aug 17, 2026Call transcriptions may be delayedThe team delivered a fix for the call transcriptions and they are slowly recovering. The third party outage is still happening but should affect the transcriptions at this time.1h 21mResolved
Jun 29, 2026Degraded performance and elevated calling errorsIssue has been fixed.3 minResolved
Jun 18, 2026Partial System OutageThe infrastructure issue affecting calling, dashboard, analytics, and other parts of our system has been fully resolved. All services are now operating normally. We sincerely apologize for the disruption and thank you…1h 59mResolved
Jun 8, 2026Campaigns loading issuesWe have applied a fix, we are monitoring the situation.9 minResolved
Apr 27, 2026Outage of outbound calls to Czech mobile and landline numbersIssue has been fully resolved.2h 40mResolved
Apr 14, 2026Partial System OutageThe infrastructure issue affecting calling, dashboard, analytics, and other parts of our system has been fully resolved. All services are now operating normally. We sincerely apologize for the disruption and thank you…1h 39mResolved
Apr 9, 2026Call Processing DelaysThe incident has been resolved. Full functionality has been restored.1h 6mResolved
Apr 1, 2026Issues with inbound calls outside EU regionService is operating normally across all areas.3h 12mResolved
Feb 25, 2026Delayed call processingThe situation is resolved, our systems have caught up with synchronizing delayed data.34 minResolved
Feb 23, 2026Issues with inbound calls to groupsOn 19 February 2026 at 09:40 CET, we experienced an incident where **a portion of inbound calls to call groups did not reach available agents and were not connected**. **Impact:** Some inbound group calls were not…-5995 minResolved
Jan 21, 2026Agent Statuses Are Not Updating Resulting in Inbound Calls Not RingingThe implemented fix is functional and the incident has been resolved.21h 25mResolved
Jan 14, 2026Slow call history updatesThe situation is resolved, our systems will process the missing records in following hours.3h 23mResolved
Dec 16, 2025Browser-based calling issues in Google Chrome 143A fix has been released2h 24mResolved
Dec 5, 2025Intermitent issues accessing CloudTalk web services following the Cloudflare outagesThe Cloudflare problems have been resolved on Friday, 5th of December10 minResolved
Dec 2, 2025Outbound VoiceAgent Calls not being triggeredIssue has been resolved.30 minResolved
Nov 18, 2025Intermitent issues accessing CloudTalk web services following the Cloudflare outages The Cloudflare problems have been resolved on Tuesday, the, the 18th of November19h 37mResolved
Nov 10, 2025Outbound VoiceAgent calls not being triggeredAll VoiceAgent calls are now triggered as expected.44h 13mResolved
Nov 7, 2025Contact Management and Tagging FailingWe have resolved the problem with contacts; everything is working as expected now. Preventive measures will be implemented to prevent recurrences1h 42mResolved
Nov 6, 2025Call Quality Issues From and to Subset of Numbers in the United Kingdom - external carrier problemThe issue affecting call quality in the United Kingdom has been resolved by the transit carriers, and the service is functioning normally at this time.18h 56mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next CloudTalk incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This CloudTalk Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CloudTalk acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single CloudTalk outage in this window ran 4d 11h, against a mean recovery of 11h 49m. If you depend on CloudTalk in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.