Channel.io Outage History

Started Sep 23, 2026, 08:52 AM UTC· resolved Sep 24, 2026, 04:54 PM UTC

1. investigating Sep 23, 2026, 08:52 AM UTC

   Temporary issue has been detected with CoS feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Sep 24, 2026, 09:36 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 06:02 AM UTC· resolved Sep 01, 2026, 07:37 AM UTC

1. investigating Sep 01, 2026, 06:02 AM UTC

   Temporary issue has been detected with Customer Support (Inbox) feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Sep 01, 2026, 07:37 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Sep 01, 2026, 05:02 AM UTC· resolved Sep 01, 2026, 07:00 AM UTC

1. investigating Sep 01, 2026, 05:02 AM UTC

   Temporary issue has been detected with Marketing feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Sep 01, 2026, 07:37 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Aug 07, 2026, 01:30 AM UTC· resolved Aug 07, 2026, 01:32 AM UTC

1. investigating Aug 07, 2026, 01:30 AM UTC

   Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Aug 07, 2026, 01:41 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Aug 04, 2026, 11:34 AM UTC· resolved Aug 04, 2026, 11:22 PM UTC

1. investigating Aug 04, 2026, 11:34 AM UTC

   CoS and Notebook are temporarily unavailable exclusively for data provided by default in Channel Talk. As a result, CoS and Notebook features using data such as user, userchat, events, and manager, as well as orders, cart_items, and products data from the Cafe24 app, are not functioning properly. - Notebooks already built with the relevant data will only display data prior to 8:00 PM UTC+9. - Default consultation statistics, Custom Reports, and CoS/Notebook analyses using custom-integrated data are unaffected. - Cafe24 app functions and task executions are also unaffected. - We will provide further notice upon completion of maintenance. We sincerely apologize for the inconvenience.

2. resolved Aug 04, 2026, 11:22 PM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 23, 2026, 07:11 AM UTC· resolved Jun 23, 2026, 08:16 AM UTC

1. investigating Jun 23, 2026, 07:11 AM UTC

   Temporary issue has been detected with Kakao Talk Integration Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Jun 23, 2026, 08:16 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 22, 2026, 06:15 AM UTC· resolved Jun 22, 2026, 06:19 AM UTC

1. investigating Jun 22, 2026, 06:15 AM UTC

   Channel Talk system is experiencing an issue. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Jun 22, 2026, 06:19 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 05, 2026, 05:30 AM UTC· resolved Jun 05, 2026, 05:30 AM UTC

1. resolved Jun 05, 2026, 05:49 AM UTC

   Temporary issue has been detected with AI ALF feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Read the full incident report →

Started May 26, 2026, 12:49 AM UTC· resolved May 26, 2026, 06:37 AM UTC

1. investigating May 26, 2026, 12:49 AM UTC

   Temporary issue has been detected with SMS Sending Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. monitoring May 26, 2026, 02:41 AM UTC

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

3. investigating May 26, 2026, 06:36 AM UTC

   Temporary issue has been detected with SMS Sending Service. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

4. resolved May 26, 2026, 06:37 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 24, 2026 04:00 ~ May 26, 2026 10:50 (KST) (approximately 2 days 6 hours 50 minutes) - Affected Scope: Domestic SMS sending via the marketing and follow-up notification features - Cause: During an internal system maintenance, SMS processing was not resumed, resulting in a failure to deliver text messages. - Resolution: SMS processing has been resumed and the service has been restored. Two-stage monitoring has been added to prevent recurrence.

Read the full incident report →

Started May 04, 2026, 01:00 AM UTC· resolved May 04, 2026, 01:00 AM UTC

1. resolved May 04, 2026, 08:56 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: May 4, 2026 09:59 ~ 13:17 (KST) (approximately 3 hours 18 minutes) - Affected Scope: Intermittent delays and failures in customer contact lookups and marketing recipient lookups in some channels during the incident period - Cause: Load was concentrated on some servers handling data, causing temporary delays and intermittent failures - Resolution: Initial load balancing has been completed, and additional stabilization work will follow. Temporary issue has been detected with Contacts feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Read the full incident report →

Started Apr 24, 2026, 06:00 AM UTC· resolved Apr 27, 2026, 02:45 PM UTC

1. investigating Apr 27, 2026, 08:50 AM UTC

   Temporary issue has been detected with AI ALF Statistics feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Apr 28, 2026, 06:19 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Apr 24, 2026, 12:39 AM UTC· resolved Apr 24, 2026, 02:11 AM UTC

1. investigating Apr 24, 2026, 12:39 AM UTC

   We are currently experiencing a temporary issue with the Channel Talk service. We have identified an issue where users are unable to log in on Android mobile devices after a new login or logging out. We are urgently investigating the cause and will provide updates as soon as possible. We sincerely apologize for any inconvenience this may cause.

2. resolved Apr 24, 2026, 02:11 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time: 2026-04-23 19:44 ~ 2026-04-24 11:05 (KST) -Affected Scope: Users who launched the Android app while in a logged-out state. -Cause: Following a server update, an issue occurred where the app entered an unexpected path during the launch process while not logged in. -Resolution: Reverted the server to its previous state and updated the Android app. -Measures to Prevent Recurrence: Strengthen pre-deployment testing for scenarios that could cause the app to freeze or hang during the launch process.

Read the full incident report →

Started Feb 13, 2026, 08:52 AM UTC· resolved Feb 13, 2026, 09:06 AM UTC

1. investigating Feb 13, 2026, 08:52 AM UTC

   We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Feb 13, 2026, 09:06 AM UTC

   The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: February 13, 2026, 16:42 – 18:04 (KST) - Affected Scope: Unable to download statistics, Custom Report data, and ALF statistics conversation lists. - Cause: A field name entry error occurred during deployment while adding summary message content. - Resolution: The related deployment changes were reverted to their previous state.

Read the full incident report →

Started Jan 13, 2026, 05:40 AM UTC· resolved Feb 27, 2026, 08:31 AM UTC

1. investigating Jan 13, 2026, 05:40 AM UTC

   Temporary issue has been detected with Customer Support (Inbox) feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. investigating Jan 13, 2026, 09:38 AM UTC

   We would like to inform you that an issue has been identified with some files uploaded to the Channel Talk media server. This issue has affected a limited number of channels. Incident Period - January 13, 2026, approximately 13:30 – 14:40 (KST) While files uploaded after 14:40 (KST) are working as intended, features using files uploaded prior to this time may still experience issues. Scope of Impact - Workflows, Marketing, and ALF (Profile images, Tasks): Files such as images, videos, and PDFs used in these features may not be displayed correctly. - Macros: If a macro contains uploaded images or files, the macro message may fail to send. - Inbox/Team Chat: Files exchanged within these areas may not be displayed correctly. Action Taken by Channel Team - Marketing campaigns with affected files have been deactivated. - We are currently investigating the possibility of recovering affected workflow files. Recommended Immediate Action - For currently affected items, you can restore normal operation immediately by re-uploading the files in their respective locations. - We apologize for the inconvenience and kindly ask you to follow this method for a quick resolution while our team continues to work on a fundamental fix. We are committed to resolving this issue as quickly as possible and will provide further updates as they become available. Depending on the impact, we may issue additional notices or contact affected channels individually to minimize any further inconvenience. If you need to check if your channel is affected or have any questions, please contact the Channel Team.

3. identified Jan 14, 2026, 08:22 AM UTC

   [Important] Apology and Action Plan Regarding Media File Deletion in Channel Talk Dear Customers, This is the Channel Team. First and foremost, we would like to offer our deepest apologies to all our customers who trust and use our services. On January 13, 2026, between 13:30 and 14:40 (KST), an issue occurred where media files (images, audio, attachments, etc.) stored in certain channels were deleted. This was due to insufficient verification and control procedures during an internal file deletion process. We take the protection of our customers' valuable data as our highest priority, and we are deeply pained that such an incident has occurred. Our entire team takes full responsibility for this matter. [Identified Issues and Scope of Impact] Phenomenon: Inability to view, play, or download certain previously uploaded media files. Scope: 1. Partial images and attachments in conversations (Team Chat, User Chat) 2. Images and attachments within Workflows, Macros, Marketing Campaigns, and ALF Tasks 3. Profile, Cover, and Custom Button images, etc. ※ Please note that critical data, including text messages, consultation history, and customer information, has NOT been deleted and remains securely stored and operational. [Recovery Status and Requests] We are currently mobilizing all available technical resources to attempt recovery. Further verification is required to determine the exact scope of the impact and the possibility of recovery. We plan to provide a more detailed update by tomorrow. If you have files that are urgently needed for your business operations, we kindly ask you to re-upload them. For any files that are confirmed to be recoverable, we will proceed with automatic recovery immediately without requiring separate requests from customers. [Future Actions and Timeline] We have activated a company-wide emergency response system. -Jan 14, 2026: Announcement of the media file deletion incident -Jan 15, 2026: Provision of a dedicated page to check the impact scope for each customer -Jan 16 – 19, 2026: Additional recovery efforts and individual support for affected customers -Jan 21 – 23, 2026: Sharing of a detailed technical report, including the root cause and recurrence prevention measures All technical recovery measures are being prioritized. Once the scope of damage is clearly defined, we will promptly review and announce a compensation plan. We consider this issue to be entirely our responsibility and sincerely apologize once again for the inconvenience and concern this has caused. We will take full responsibility and do our best to minimize the impact and prevent this from happening again. Sincerely, Channel Team

4. monitoring Jan 22, 2026, 06:26 AM UTC

   We sincerely apologize to all customers affected by the file deletion issue. Below is the technical report outlining the details of the incident. Summary - Incident period: January 12, 2026 (Mon), 11:28 PM – January 13, 2026 (Tue), 12:43 AM (EST) - Scope of impact: Media files (images, audio, attachments, etc.) stored in some channels Cause and Impact This incident was not caused by an external factor or system infrastructure failure, but by insufficient internal operational procedures and validation. On January 13, 2026, during a scheduled cleanup of files that had reached their retention period, a code error resulted in files being deleted beyond the intended scope. The root cause was the lack of adequate pre-validation of the impact scope, insufficient verification of deletion targets, and the absence of safety mechanisms for recovery. As a result, the following issues occurred: - Silent audio in inbound call features (e.g., IVR and guidance messages) due to failed audio file references - Inability to view files used in macros, profiles, cover images, and custom button images - Inability to view files within one time message, campaigns, workflows, and ALF tasks - Inability to view images and attachments in team chats and user chats Actions Taken and Recovery Status - Immediately halted the file deletion logic upon detection and rolled back the system to a previous stable version - Temporarily disabled certain related features to prevent further impact - Sequentially completed recovery of voice-related features, including TTS and IVR - Provided and operated a dedicated guidance page allowing customers to review deleted files and re-register them as needed Preventive Measures To prevent similar incidents from recurring, we have immediately implemented the following measures: - Mandatory pre-impact analysis and approval processes for all destructive actions, such as file deletion - Introduction of pre-execution visualization and confirmation of deletion targets - Implementation of a multi-approval–based operational policy In addition, we will conduct a comprehensive review of our file management system and continue to improve our operational processes.

5. resolved Feb 27, 2026, 08:31 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 13, 2026, 04:30 AM UTC· resolved Jan 13, 2026, 04:30 AM UTC

1. resolved Jan 15, 2026, 05:07 AM UTC

   We would like to inform you that the temporary issue affecting the marketing feature has been resolved, and the service is now back to normal and available for use. We apologize for any inconvenience caused. Incident Time: 2026. 01. 09 21:00 ~ 2026. 01. 13 13:30 (KST) Affected Scope: All marketing campaigns using marketing and offline email follow-ups. Cause: Email follow-ups via marketing failed to function during core logic modifications. Resolution: Fixed the core logic. Measures to Prevent Recurrence: Establish a structure that enables the marketing pipeline to detect and respond to core logic changes.

Read the full incident report →

Started Dec 19, 2025, 01:50 AM UTC· resolved Dec 19, 2025, 02:02 AM UTC

1. investigating Dec 19, 2025, 01:50 AM UTC

   현재 Channel Talk 시스템에 문제가 발생하고 있습니다. 현재 원인을 조사 중이며, 조속히 업데이트를 안내드리겠습니다. 이용에 불편을 드려 죄송합니다. Channel Talk system is experiencing an issue. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Dec 19, 2025, 02:02 AM UTC

   안녕하세요, 채널톡입니다. 오늘 오전 약 10분간 접속 불가 문제가 발생하여 이용에 불편을 드린 것에 대해 깊이 사과드립니다. 해당 접속 불가 문제는 계정 보안 및 인증 강화와 관련된 서버 부하로 확인되었습니다. 채널톡 업데이트 배포는 안정적인 사용성 제공을 위해 사용량이 보편적으로 가장 적은 늦은 저녁부터 새벽 사이에 진행하고 있고, 어제 밤부터 새벽 사이 보안 관련 안전한 사용 환경을 제공하기 위해 계정 보안 및 인증 강화와 관련된 배포 작업을 진행했습니다. 자세한 내용은 아래 장애 상세 경위 및 조치 내용을 확인해 주시기 바랍니다. 다시 한번 이용에 불편을 드려 죄송합니다. 채널팀 드림 상세 경위 -발생 시간: 2025.12.19 10:44 - 20205.12.19 10:56 (KST) -영향 범위: 계정 인증을 필요로 하는 채널톡 내 모든 API 에 대해 일시적 요청 실패 및 강제 로그아웃 -원인: 계정 보안 고도화를 위한 인증 시스템 강화 관련 배포 이후, 서버 부하 발생 시 작동되어야 할 자동 서버 확충 시스템이 작동되지 않아 발생 -조치 내용: 관련 서버 수동 확충 및 안정화를 위한 서버 자동 확충 로직 수정 조치 -재발 방지 대책: 에러 지점에 대한 지표 수집 및 알람 설정 강화 Hello, this is Channel Talk. We sincerely apologize for the inconvenience caused by a connection issue that occurred this morning for approximately 10 minutes. The issue was identified as a server overload related to enhancing account security and authentication. To ensure stable service, Channel Talk updates are typically deployed late at night or in the early morning when usage is lowest. Last night, we performed a deployment to strengthen account security and authentication to provide a more secure user environment. For more details, please see the incident report and actions taken below. Once again, we apologize for the inconvenience. Sincerely, The Channel Team Incident Details -Incident Time: 2025.12.19 10:44 - 2025.12.19 10:56 (KST) -Affected Scope: Temporary request failures and forced logouts for all APIs within Channel Talk that require account authentication. -Cause: Following a deployment to enhance the authentication system for advanced account security, the automatic server scaling system, which should have activated during a server load spike, failed to operate. -Resolution: We manually scaled the relevant servers and modified the auto-scaling logic to ensure stability. -Measures to Prevent Recurrence: We will enhance metric collection and strengthen alarm settings for the point of failure.

Read the full incident report →

Started Dec 19, 2025, 01:26 AM UTC· resolved Dec 19, 2025, 07:31 AM UTC

1. investigating Dec 19, 2025, 01:26 AM UTC

   수신함 기능에 일시적인 문제가 발견되어 안내드립니다. 현재 신속한 조치중이며, 복구 시 안내드리도록 하겠습니다. 이용에 불편을 드려 죄송합니다. 발견된 증상: 일부 또는 전체 고객 정보가 "알 수 없음"으로 표시됨. Temporary issue has been detected with Customer Support (Inbox) feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause. Discovered issue: Some or all customer information is displayed as "Unknown".

2. resolved Dec 19, 2025, 07:31 AM UTC

   일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Dec 19, 2025, 12:46 AM UTC· resolved Dec 19, 2025, 01:59 AM UTC

1. investigating Dec 19, 2025, 12:46 AM UTC

   상담별 통계 조회에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. -발견된 증상: 기간 필터링이 25/12/13~25/12/19로 고정됨. Temporary issue has been detected with Analytics feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause. -Discovered issue: The date range filter is fixed/stuck on 25/12/13~25/12/19.

2. resolved Dec 19, 2025, 01:59 AM UTC

   상담별 통계 조회와 관련한 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. Temporary issue has been detected with Analytics feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Read the full incident report →

Started Dec 05, 2025, 05:11 AM UTC· resolved Dec 05, 2025, 05:23 AM UTC

1. investigating Dec 05, 2025, 05:11 AM UTC

   고객 상담 화면에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. Temporary issue has been detected with Customer Support Interface. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Dec 05, 2025, 05:30 AM UTC

   일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 2025. 12. 05 14:00 ~ 2025. 12. 05 14:23 (KST) -영향 범위: 프론트(고객사의 고객) 기능 마비 -원인: 해당 시간에 외부 연동 주문 처리에 대한 고객정보 업데이트 요청이 대량으로 몰려 서버에서 처리 트래픽에 병목 현상이 발생하였습니다. -조치 내용: 해당 요청이 발생한 대상의 boot 성공 비율 조절로 트래픽을 일시적으로 조절하여 트래픽이 감소하도록 조치하였습니다. -재발 방지 대책: - 내년 1~2월 중으로 요청 병목 현상에 대한 근본적인 원인 개선 배포를 준비중입니다. - 근본 개선 전에, 외부 연동 주문 처리에 의한 트래픽 병목에 대한 처리 속도 조절 메커니즘을 도입할 예정입니다. (1~2주 내로 진행하는 것을 목표로 하고 있습니다.) The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time: 2025. 12. 05 14:00 ~ 2025. 12. 05 14:23 (KST) -Affected Scope: Outage of front-end features (for our clients' customers). -Cause: A large volume of customer profile update requests related to external order processing caused a traffic bottleneck on the server. -Resolution: We temporarily reduced the traffic by adjusting the boot success rate for the affected service where the requests originated. -Measures to Prevent Recurrence: -We are preparing a deployment to fundamentally resolve the request bottleneck issue, scheduled for January-February of next year. -Before this fundamental fix, we will introduce a rate-limiting mechanism to manage traffic bottlenecks caused by external order processing. (We aim to implement this within 1-2 weeks.)

Read the full incident report →

Started Nov 28, 2025, 01:47 AM UTC· resolved Nov 28, 2025, 02:16 AM UTC

1. investigating Nov 28, 2025, 01:47 AM UTC

   전화 기능에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Nov 28, 2025, 02:16 AM UTC

   일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 2025. 11. 28 08:41 ~ 2025. 11. 28 10:55 (KST) -영향 범위: 전화 미트를 이용하는 모든 고객 -원인: 서버 웹훅 유실로 인해 전화 종료 로직이 수행되지 않았습니다. -조치 내용: 원인이 된 서버를 롤백하였습니다. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time: 2025. 11. 28 08:41 ~ 2025. 11. 28 10:55 (KST) -Affected Scope: All customers using Phone Meet. -Cause: The call termination logic did not execute due to a loss of server webhooks. -Resolution: The server that caused the issue has been rolled back.

Read the full incident report →

Started Nov 25, 2025, 08:14 AM UTC· resolved Nov 25, 2025, 10:07 AM UTC

1. investigating Nov 25, 2025, 08:14 AM UTC

   통화 종료 시 '응답대기중'으로 보여지는 문제와 이로 인해 신규 전화 수신이 불가한 문제가 발견되었습니다. 현재 원인 확인되었으며 1시간 이내로 해결 예정입니다. 불편을 드려 죄송합니다. Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Nov 26, 2025, 01:49 AM UTC

   일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 발생 시간: 2025. 11. 24 ~ 2025. 11. 25 10:34 (KST) -영향 범위: 종료된 전화에 대해서 상담 상태가 연결 중으로 보이거나 오퍼레이터 상태가 통화중으로 보임 -원인: 유저, 매니저가 미트에서 나갔다는 이벤트를 받아야 통화가 정상적으로 종료되는데 해당 이벤트가 유실되어서 서버에서 받지 못함 -조치 내용: 별도의 전화 종료 이벤트를 추가해서 통화 상태를 종료로 변경하도록 방어 로직 추가 The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Nov 25, 2025, 05:58 AM UTC· resolved Nov 25, 2025, 06:18 AM UTC

1. investigating Nov 25, 2025, 05:58 AM UTC

   일본 국가 채널의 전화 기능 발신에 문제가 발견되었습니다. Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Nov 25, 2025, 06:18 AM UTC

   일본 국가 채널에 발생하던 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Nov 21, 2025, 12:50 AM UTC· resolved Nov 21, 2025, 12:50 AM UTC

1. investigating Nov 21, 2025, 12:37 AM UTC

   전화 자동 배정 기능에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. Temporary issue has been detected with Meet Auto-Assignment feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

2. resolved Nov 21, 2025, 01:11 AM UTC

   일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 2025. 11. 20 20:00 ~ 2025. 11. 21 09:50 (KST) -영향 범위: 팀 배정 및 담당자 자동배정이 동작하는 전화상담 중, 담당자 배정이 완료되었음에도 전화 배정이 가능한 모든 매니저 대상으로 링이 울리는 증상. -원인: 11월 20일 20시 배포에 포함된 자동배정 로직 코드 수정 작업으로 인한 영향. -조치 내용: 증상 인지 후 문제의 원인이 포함된 배포에 대한 롤백 진행 The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time: 2025. 11. 20 20:00 ~ 2025. 11. 21 09:50 (KST) -Affected Scope: For phone calls using automatic team and Assignee assignment, the call would ring for all available managers, even after an Assignee was successfully assigned. -Cause: The issue was caused by a modification to the auto-assignment logic code included in the deployment on November 20th at 20:00. -Resolution: Upon identifying the issue, we rolled back the deployment that contained the problematic code.

Read the full incident report →

Started Nov 05, 2025, 01:57 AM UTC· resolved Nov 05, 2025, 01:57 AM UTC

1. resolved Nov 05, 2025, 01:57 AM UTC

   전화 수신시 일부 채널에서 연결 불가, 지연이 되는 상황이 발생하였습니다. 현재 서비스는 정상화 되어 이용이 가능함을 안내드립니다. 이용에 불편을 드려 죄송합니다. Temporary issue has been detected with Phone feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Read the full incident report →

Started Oct 20, 2025, 07:50 AM UTC· resolved Oct 21, 2025, 01:38 AM UTC

1. investigating Oct 20, 2025, 07:50 AM UTC

   트윌리오 계정을 사용해 해외 고객에게 발송되는 문자 (마케팅, 팔로업 알림) 발송에 일시적인 문제가 발견되었습니다. 트윌리오 측 장애로 확인되며, 불편을 드려 죄송합니다. 자세한 내용은 트윌리오 stauspage를 함께 확인해주시기 바랍니다. https://status.twilio.com/ We have identified a temporary issue affecting SMS messages (marketing and follow-up notifications) sent to international customers via our Twilio account. The incident has been confirmed to be on Twilio’s side, and we apologize for the inconvenience. For more details, please refer to Twilio’s status page: https://status.twilio.com/

2. investigating Oct 20, 2025, 07:56 AM UTC

   We are continuing to investigate this issue.

3. resolved Oct 21, 2025, 01:38 AM UTC

   트윌리오 서비스의 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 자세한 내용은 트윌리오 stauspage를 함께 확인해주시기 바랍니다. https://status.twilio.com/ The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. For more details, please refer to Twilio’s status page: https://status.twilio.com/

Read the full incident report →