Cloudtalk 장애 기록

1. 2026년 10월 13일 오전 11:07 UTCmonitoring

   우리는 우리의 AI 공급자, ElevenLabs의 서비스를 가진 문제점을 경험하고 있습니다. 사용자의 하위 설정은 영향을 받고 우리 팀은 적극적으로 상황을 모니터링합니다. 더 많은 정보를 더 많이 제공 할 것입니다. Deepgram을 사용하여 VoiceAgents는 공급자가 비범합니다.

2. 2026년 10월 13일 오후 1:23 UTCmonitoring

   우리는 여전히 AI 공급 업체 중 하나 인 ElevenLabs의 서비스를 통해 문제가 있습니다. 더 많은 정보를 더 많이 제공 할 것입니다.

3. 2026년 10월 13일 오후 2:06 UTCmonitoring

   우리는 여전히 AI 공급 업체 중 하나 인 ElevenLabs의 서비스를 통해 문제가 있습니다. 더 많은 정보를 더 많이 제공 할 것입니다. 공급자로 ElevenLabs를 사용하여 VoiceAgents의 구성 변경은 이 시간에 처리되지 않습니다.

4. 2026년 10월 13일 오후 2:39 UTCresolved

   ElevenLabs의 문제, 우리의 AI 공급자 중 하나, 해결됩니다. 모든 VoiceAgent 기능은 다시 안정적입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 오후 3:20 UTCidentified

   우리는 현재 우리의 모델 제공 업체 중 하나에 영향을 미치는 지속적인 제 3 자 정전 때문에 전화 쓰레기와 지연을보고 있습니다. 우리의 팀은 완화를 신청하고 우리는 backlog가 명확하게 되기 때문에 갱신을 곧 포스트할 것입니다.

2. 2026년 8월 17일 오후 4:41 UTCresolved

   팀은 전화 쓰레기통에 대한 수정을 전달하고 천천히 회복합니다. 세 번째 파티 아웃은 여전히 일어나지 만이 시간에 쓰레기에 영향을 미칩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 29일 오후 4:00 UTCidentified

   We're experiencing an elevated level of calling errors and are currently looking into the issue. We are reverting faulty deployments of our services.

2. 2026년 6월 29일 오후 4:03 UTCresolved

   Issue has been fixed.

1. 2026년 6월 18일 오후 2:16 UTCinvestigating

   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.

2. 2026년 6월 18일 오후 2:49 UTCinvestigating

   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.

3. 2026년 6월 18일 오후 3:16 UTCinvestigating

   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**.

4. 2026년 6월 18일 오후 3:48 UTCinvestigating

   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**.

5. 2026년 6월 18일 오후 4:16 UTCresolved

   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.

1. 2026년 6월 8일 오전 8:26 UTCidentified

   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.

2. 2026년 6월 8일 오전 8:36 UTCresolved

   We have applied a fix, we are monitoring the situation.

1. 2026년 4월 27일 오전 8:07 UTCinvestigating

   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.

2. 2026년 4월 27일 오전 8:10 UTCidentified

   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.

3. 2026년 4월 27일 오전 10:47 UTCresolved

   Issue has been fully resolved.

1. 2026년 4월 14일 오후 2:44 UTCinvestigating

   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.

2. 2026년 4월 14일 오후 2:59 UTCinvestigating

   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.

3. 2026년 4월 14일 오후 3:29 UTCinvestigating

   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.

4. 2026년 4월 14일 오후 3:46 UTCmonitoring

   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.

5. 2026년 4월 14일 오후 4:23 UTCresolved

   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.

1. 2026년 4월 9일 오후 4:22 UTCinvestigating

   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.

2. 2026년 4월 9일 오후 4:27 UTCmonitoring

   The root cause of the incident has been identified, and steps have been taken to resolve the issue.

3. 2026년 4월 9일 오후 5:29 UTCresolved

   The incident has been resolved. Full functionality has been restored.

1. 2026년 4월 1일 오전 8:26 UTCidentified

   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.

2. 2026년 4월 1일 오전 8:52 UTCmonitoring

   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.

3. 2026년 4월 14일 오후 4:19 UTCresolved

   Service is operating normally across all areas.

1. 2026년 2월 25일 오후 4:00 UTCinvestigating

   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.

2. 2026년 2월 25일 오후 4:35 UTCresolved

   The situation is resolved, our systems have caught up with synchronizing delayed data.

1. 2026년 2월 23일 오후 12:35 UTCresolved

   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.

1. 2026년 1월 21일 오후 5:44 UTCinvestigating

   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.

2. 2026년 1월 21일 오후 6:20 UTCmonitoring

   The issue has been identified and a fix has been implemented.

3. 2026년 1월 22일 오후 3:09 UTCresolved

   The implemented fix is functional and the incident has been resolved.

1. 2026년 1월 14일 오후 4:08 UTCidentified

   We are experiencing slower processing of calls causing some recent calls not visible in the call history.

2. 2026년 1월 14일 오후 7:32 UTCresolved

   The situation is resolved, our systems will process the missing records in following hours.

1. 2025년 12월 16일 오전 10:33 UTCinvestigating

   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.

2. 2025년 12월 16일 오후 12:58 UTCresolved

   A fix has been released

1. 2025년 12월 5일 오전 9:04 UTCinvestigating

   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/")

2. 2025년 12월 5일 오전 9:14 UTCresolved

   The Cloudflare problems have been resolved on Friday, 5th of December

1. 2025년 12월 2일 오후 1:15 UTCidentified

   We have identified an issue with the Outbound VoiceAgent calls which are not being triggered. The team is working on a fix.

2. 2025년 12월 2일 오후 1:34 UTCmonitoring

   A fix has been released and the team is monitoring the situation.

3. 2025년 12월 2일 오후 1:46 UTCresolved

   Issue has been resolved.

1. 2025년 11월 18일 오후 1:32 UTCidentified

   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/

2. 2025년 11월 19일 오전 9:09 UTCresolved

   The Cloudflare problems have been resolved on Tuesday, the, the 18th of November

1. 2025년 11월 10일 오후 4:46 UTCidentified

   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.

2. 2025년 11월 10일 오후 5:21 UTCmonitoring

   All VoiceAgent calls are now triggered as expected. We're monitoring the released fix.

3. 2025년 11월 13일 오전 7:00 UTCresolved

   All VoiceAgent calls are now triggered as expected.

1. 2025년 11월 7일 오전 11:00 UTCinvestigating

   **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.

2. 2025년 11월 7일 오후 12:43 UTCresolved

   We have resolved the problem with contacts; everything is working as expected now. Preventive measures will be implemented to prevent recurrences

1. 2025년 11월 6일 오후 2:59 UTCidentified

   **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.

2. 2025년 11월 7일 오전 9:55 UTCresolved

   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.