27 incidente Cloudtalk înregistrate începând din septembrie 2025, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
We're experiencing an elevated level of calling errors and are currently looking into the issue. We are reverting faulty deployments of our services.
Issue has been fixed.
We're currently experiencing an infrastructure issue affecting **calling, dashboard, analytics, and other parts of our system.** Our team is actively investigating and working to resolve it as quickly as possible. We apologize for the inconvenience and will share further updates every 30 minutes.
We're still experiencing an infrastructure issue affecting **calling, dashboard, analytics, and other parts of our system.** Our team has identified the issue and is actively working on resolving it. We expect to restore the system stability within the next 90 minutes.
We're still experiencing an infrastructure issue affecting **calling, dashboard, analytics, and other parts of our system.** Our team has identified the issue and is actively working on resolving it. We expect to restore the system stability within the next **60 minutes**.
We're still experiencing an infrastructure issue affecting **calling, dashboard, analytics, and other parts of our system.** Our team has identified the issue and is actively working on resolving it. We expect to restore the system stability within the next **30 minutes**.
The 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 for your patience. Our team will continue to monitor the platform to ensure stability.
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.
We have applied a fix, we are monitoring the situation.
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.
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.
Issue has been fully resolved.
We are currently experiencing an infrastructure issue affecting **calling, the dashboard, analytics, and other parts of our system**. Our team is actively investigating and working to resolve this as quickly as possible. We apologize for the inconvenience and will share a further update once the issue is resolved.
We are currently experiencing an infrastructure issue affecting calling, the dashboard, analytics, and other parts of our system. Our team is actively investigating and working to resolve this as quickly as possible. We apologize for the inconvenience and will share a further update once the issue is resolved.
We are currently experiencing an infrastructure issue affecting calling, the dashboard, the analytics, and other parts of our system. Our team identified the issue and is working to resolve it as quickly as possible. We apologize for the inconvenience and will share a further update once the issue is resolved.
We have implemented a fix for the infrastructure issue that was affecting **calling, dashboard, analytics, and other parts of our system**. Service is now recovering across all affected areas. Our team is actively monitoring the situation to ensure full stability is restored. We will share a further update shortly.
The 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 for your patience. Our team will continue to monitor the platform to ensure stability.
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.
The root cause of the incident has been identified, and steps have been taken to resolve the issue.
The incident has been resolved. Full functionality has been restored.
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.
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.
Service is operating normally across all areas.
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.
The situation is resolved, our systems have caught up with synchronizing delayed data.
On 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 successfully routed to online agents during the incident window. Other call types were not affected. **Root cause:** The issue was caused by a recent configuration change in our call routing layer. The change modified the routing logic responsible for delivering inbound calls to the system component that connects calls to agents, which resulted in certain calls not being properly forwarded. **Resolution:** The configuration change was reverted, restoring the previous routing logic. Call routing returned to normal operation, and we have confirmed stable behavior since resolution. **Preventive measures:** We are reviewing our change validation procedures to strengthen safeguards around routing-layer updates and reduce the risk of similar incidents in the future. We apologize for the disruption and appreciate your patience.
We’re experiencing issues with our service. All users are impacted and our team is actively working to resolve this. We will provide more details as soon as more information becomes available.
The issue has been identified and a fix has been implemented.
The implemented fix is functional and the incident has been resolved.
We are experiencing slower processing of calls causing some recent calls not visible in the call history.
The situation is resolved, our systems will process the missing records in following hours.
We have identified an issue affecting browser-based calling caused by a recent update to Google Chrome (version 143). Due to this change, the **hold and unhold functionality is not working correctly**. When a call is placed on hold and then resumed, the call may become inactive, resulting in a dead call and the user being stuck on the calling screen. This issue also impacts **warm transfers and three-way calling**, as they rely on the same underlying behavior. Our engineering team has successfully reproduced the issue and is actively working on a fix. We will provide an update as soon as a fix is available. **Workaround:** If you experience issues with hold, unhold, warm transfer, or three-way calling, please use the **desktop application**, which continues to work as expected.
A fix has been released
CLOUDFLARE, a global leader in web service security, is affected by a major outage [https://www.cloudflarestatus.com/](https://www.cloudflarestatus.com/ "https://www.cloudflarestatus.com/") Various web services, including CloudTalk dashboards, are affected by intermittent issues; users are unable to access the service intermittently, and the server is responding with various errors (500). The CloudTalk services remain unaffected; only the access may be unavailable for periods of time. We are monitoring the services and advise the customers to watch this page and [https://www.cloudflarestatus.com/](https://www.cloudflarestatus.com/ "https://www.cloudflarestatus.com/")
The Cloudflare problems have been resolved on Friday, 5th of December
We have identified an issue with the Outbound VoiceAgent calls which are not being triggered. The team is working on a fix.
A fix has been released and the team is monitoring the situation.
Issue has been resolved.
CLOUDFLARE, a global leader in web service security, is affected by a major outage https://www.cloudflarestatus.com/ Various web services, including CloudTalk dashboards, are affected by intermittent issues; users are unable to access the service intermittently, and the server is responding with various errors (500). The CloudTalk services remain unaffected; only the access may be unavailable for periods of time. We are monitoring the services and advise the customers to watch this page and https://www.cloudflarestatus.com/
The Cloudflare problems have been resolved on Tuesday, the, the 18th of November
We have identified an issue with VoiceAgent calls that is impacting all Outbound call attempts, causing them not to be triggered. The team is implementing a fix and expect it to be released in the next 30 minutes.
All VoiceAgent calls are now triggered as expected. We're monitoring the released fix.
All VoiceAgent calls are now triggered as expected.
**Impact:** Users are currently unable to add, delete, or update contacts in CloudTalk. Additionally, adding tags to contacts is not functioning as expected. **Status:** Our engineering team is actively investigating the issue and working on a fix. We’ll share an update as soon as we have more information.
We have resolved the problem with contacts; everything is working as expected now. Preventive measures will be implemented to prevent recurrences
**What’s happening** We’re seeing degraded call quality affecting a subset of inbound and outbound calls to/from the United Kingdom (+44). The issue has been traced to an upstream carrier. **Impact** Some calls may experience no audio, choppy or robotic audio, high jitter/packet loss, or intermittent one-way audio. This affects only specific ranges of numbers; most traffic is unaffected.
The issue affecting call quality in the United Kingdom has been resolved by the transit carriers, and the service is functioning normally at this time.
We are currently experiencing a **partial outage affecting inbound and outbound calls for customers in North America** and LATAM. Our engineering team has identified disruptions impacting certain carriers in the region, which may result in failed or dropped calls. We apologize for the inconvenience and appreciate your patience while we work to restore full functionality.
we have identified the root cause of the issue
The problem has been fixed, and all calls are processing normally
Incident has been resolved
We’re experiencing issues with our service in US region. The issue was affecting 1:30 to 2:30 PM UTC and we already mitigated the issue. The source of the issue was the ongoing AWS outage. Outbound and inbound calls could be disrupted during this time in US region. We'll continue monitoring the system to ensure the services remains stable.
The traffic was migrated to European region and the calls should be working fine. We're monitoring the system.
All systems calling systems are functional now