THIS IS A SCHEDULED EVENT Apr <var data-var='date'>26</var>, <var data-var='time'>04:00</var> - <var data-var='time'>04:30</var> KSTMar <var data-var='date'>26</var>, <var data-var='time'>14:52</var> KST Scheduled - To enhance service stability and security, we will be performing preparatory work for our main database (DB) upgrade. Below are the details of the scheduled maintenance. Maintenance Schedule Date: Saturday, April 25, 2026 EST / Sunday, April 26, 2026 KST Time: Starting at 2:00 PM EST / 4:00 AM KST Duration: Approximately 30 minutes Service Impact During the maintenance period, all Channel.io services will be unavailable. Services will be automatically resumed upon completion. Notice Document English: Link to be provided. 한국어: <a href="https://docs.channel.io/updates/ko/articles/%EC%A4%91%EC%9A%94-%EA%B3%B5%EC%A7%80-%EC%B1%84%EB%84%90%ED%86%A1-%EB%A9%94%EC%9D%B8-DB-%EC%97%85%EA%B7%B8%EB%A0%88%EC%9D%B4%EB%93%9C-%EC%A0%90%EA%B2%80%EC%97%90-%EB%94%B0%EB%A5%B8-%EC%84%9C%EB%B9%84%EC%8A%A4-%EC%9D%BC%EC%8B%9C-%EC%A4%91%EB%8B%A8-%EC%95%88%EB%82%B4-260426-b04d019f">link</a> 日本語: 後ほどリンクを提供いたします If you have any questions regarding this notice, please contact us via Channel.io.

[Important Notice] Scheduled Maintenance for Channel.io Main DB Upgrade Preparation

Apr <var data-var='date'> 8</var>, <var data-var='time'>15:25</var> KST Resolved - 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. 08 15:10 ~ 2026. 04. 08 15:25 (KST) - Affected Scope: Some channels using a specific LLM model (Claude) for ALF responses (List of channels attached below). - Cause: Service error (overload) from the provider of the specific LLM model. - Resolution: Switched to using a different LLM model for generating responses. - Measures to Prevent Recurrence: Plan to reduce the time required to switch LLM models in the event of a service error from the LLM provider.Apr <var data-var='date'> 8</var>, <var data-var='time'>15:24</var> KST Monitoring - A fix has been implemented and we are monitoring the results.Apr <var data-var='date'> 8</var>, <var data-var='time'>15:20</var> KST Update - We are continuing to investigate this issue.Apr <var data-var='date'> 8</var>, <var data-var='time'>15:20</var> KST Investigating - 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.

Temporary issue detected with AI ALF feature

Apr <var data-var='date'> 1</var>, <var data-var='time'>11:30</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. -Incident Time 1: 2026. 04. 01 00:00 ~ 2026. 04. 01 00:30 (KST) -Incident Time 2: 2026. 04. 01 08:30 ~ 2026. 04. 01 11:30 (KST) -Affected Scope: In some channels, ALF sent error messages instead of responses, after which the chats were transferred to managers. -Cause: System load on the external service (LLM provider) used for generating ALF responses. -Resolution: Swapped to an alternative LLM service model. -Measures to Prevent Recurrence: Establish an automatic fallback system to ensure response continuity by switching to alternative models or services if a specific provider encounters an issue.

Mar <var data-var='date'>19</var>, <var data-var='time'>21:55</var> KST Resolved - 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. 03. 19 19:41 ~ 2026. 03. 19 21:55 (KST) Affected Scope: An issue where the 'Send' button fails to activate when composing response messages in certain user chats. Cause: While disabling the 'Send' button due to configuration errors in email user chats, regular user chats (non-email) were inadvertently affected. Resolution: Modified the logic to perform the 'Send' button disable check only within the email editor.Mar <var data-var='date'>19</var>, <var data-var='time'>19:41</var> KST Identified - 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. Please note that there is an issue where the 'Send' button in the inbox input field may appear disabled in certain situations. However, messages can still be sent by pressing the 'Enter' key.

Temporary issue detected with Customer Support (Inbox)

Mar <var data-var='date'>18</var>, <var data-var='time'>14:00</var> KST Resolved - 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. 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. 03. 18 14:00 ~ 2026. 03. 23 16:00 (KST) -Affected Scope: ALF providing inaccurate responses due to failure to correctly reference linked knowledge. -Cause: An issue where certain reference information was missing in the RAG (Retrieval-Augmented Generation) logic. -Resolution: Emergency fix and deployment completed after identifying the cause; service has been restored to normal.

Mar <var data-var='date'>13</var>, <var data-var='time'>11:18</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. Issue 1: Response disruption due to Claude model quota exhaustion - Incident Time: 2026.03.13 11:11 ~ 11:18 (approximately 7 minutes) - Affected Scope: Some channels using ALF - Cause: ALF responses were not functioning properly in certain channels due to the exhaustion of the allocated quota for the Claude model. Issue 2: Service disruption caused by configuration error during model deactivation - Incident Time: 2026.03.13 11:18 ~ 11:40 (approximately 22 minutes) - Affected Scope: All channels using the ALF response feature - Cause: While disabling the Claude model for specific channels to resolve Issue 1, a configuration error caused the model setting to be applied across all channels, resulting in response disruptions. Issue 3: Response disruption due to Claude model usage control configuration - Incident Time:2026.03.13 15:16:20 ~ 15:22:50 (KST) - Affected Scope: Some channels using ALF - Cause: Due to an issue with the vendor-side control configuration for Claude model calls, ALF responses were not functioning properly in certain channels. The issue has now been resolved, and the service has been operating normally since 11:40. We sincerely apologize for the inconvenience caused.

Mar <var data-var='date'>13</var>, <var data-var='time'>11:09</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: March 12, 2026 20:32 ~ March 13, 2026 11:09 (KST) - Affected Scope: In certain cases where team assignment and VoiceALF were used together in an IVR workflow, calls connected through VoiceALF were not routed to agents when a request to connect to an agent was made. - Cause: The status change function did not operate correctly when a call waiting for a manager was moved to the queue. - Resolution: Fixed the issue so that the queue status change function operates correctly. - Measures to Prevent Recurrence: Strengthen testing across a wider range of environments.

Temporary issue detected with Phone feature

Mar <var data-var='date'> 5</var>, <var data-var='time'>20:24</var> KST Resolved - 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. 03. 05 20:18 ~ 2026. 03. 05 20:24 (KST) - Affected Scope: Connection delays and non-responsiveness on Channel Talk Desk. - Cause: A sudden surge in database connection demand occurred following improvements to the asynchronous thread pool structure, resulting in a service failure. - Resolution: Reverted to the previous thread pool structure. - Measures to Prevent Recurrence: Establish a process to pre-evaluate the impact on DB connections when modifying thread pool structures and strengthen connection-related monitoring alerts.

Service Partially Unavailable

Mar <var data-var='date'> 3</var>, <var data-var='time'>18:02</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. 1) - Incident Time: March 3, 2026 13:20 ~ March 3, 2026 15:22 (KST) - Affected Scope: ALF knowledge-based responses - Cause: Temporary resource shortage due to increased Gemini API usage - Resolution: Temporarily increased the allocated resource quota - Measures to Prevent Recurrence: Mitigate resource shortages by splitting API calls to distribute load 2) - Incident Time: March 3, 2026 16:46 ~ March 3, 2026 17:22 (KST) - Affected Scope: ALF response generation - Cause: Delay in reflecting stabilization improvements applied to ALF - Resolution: Switched to an alternative available AI platform - Measures to Prevent Recurrence: Apply redundancy mechanisms earlier to ensure uninterrupted service in case of ALF-related issuesMar <var data-var='date'> 3</var>, <var data-var='time'>17:12</var> KST Update - We are continuing to investigate this issue.Mar <var data-var='date'> 3</var>, <var data-var='time'>17:04</var> KST Investigating - 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.

Feb <var data-var='date'>27</var>, <var data-var='time'>17:31</var> KST Resolved - This incident has been resolved.Jan <var data-var='date'>22</var>, <var data-var='time'>15:26</var> KST Monitoring - 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.Jan <var data-var='date'>14</var>, <var data-var='time'>17:22</var> KST Identified - [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 TeamJan <var data-var='date'>13</var>, <var data-var='time'>18:38</var> KST Update - 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.Jan <var data-var='date'>13</var>, <var data-var='time'>14:40</var> KST Investigating - 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.

Issue regarding files uploaded to the Channel Talk media server

Feb <var data-var='date'>24</var>, <var data-var='time'>16:30</var> KST Resolved - 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. 02. 24 15:26 ~ 2026. 02. 24 16:30 (KST) -Affected Scope: VoiceALF calls in channels using Olivia and Sakura voices. -Cause: Usage limit exceeded by the ALF voice provider. -Resolution: Adjusted the usage limit of the ALF voice provider. -Measures to Prevent Recurrence: Separate ALF voice usage limits and implement logic to switch to voices from other providers if a specific provider encounters an issue.

Feb <var data-var='date'>13</var>, <var data-var='time'>18:06</var> KST Resolved - 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.Feb <var data-var='date'>13</var>, <var data-var='time'>17:52</var> KST Investigating - We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Temporary issue detected with Analytics Feature

Feb <var data-var='date'>13</var>, <var data-var='time'>16:16</var> KST Resolved - 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:16 – 16:26 (KST) Affected Scope: IB/OB calls that occurred between 16:16 and 16:26. There is a possibility of an additional 5–10 minutes of impact due to a call that occurred at 16:26. Cause: An issue occurred during server deployment while applying a fix for the intermittent recording omission issue. Resolution: Server rollback. 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.

Jan <var data-var='date'>29</var>, <var data-var='time'>21:10</var> KST Resolved - 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. 01. 29 19:05 ~ 2026. 01. 29 21:10 (KST) - Affected Scope: For customers using mobile SDK versions earlier than 12.0.0, workflows were not triggered when starting a 'new chat' via the mobile app (unable to start new inquiries). - Cause: During the removal of legacy Support Bot-related code, the API called during mobile workflow execution was inadvertently affected. - Resolution: Rolled back the deleted legacy API.

Jan <var data-var='date'>29</var>, <var data-var='time'>19:30</var> KST Resolved - 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. 01. 29 19:31 ~ 2026. 01. 29 19:46 (KST) - Affected Scope: Users with their account language set to 'Japanese' were unable to access the Desk. - Resolution: Rolled back the deployment that caused the issue. - Measures to Prevent Recurrence: Automate translation deployment during Web Desk deployment and add defensive logic for cases where translations are missing.

Jan <var data-var='date'>15</var>, <var data-var='time'>15:00</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.Jan <var data-var='date'>15</var>, <var data-var='time'>14:34</var> KST Investigating - 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.

Jan <var data-var='date'>13</var>, <var data-var='time'>21:06</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.Jan <var data-var='date'>13</var>, <var data-var='time'>14:51</var> KST Investigating - 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.

Jan <var data-var='date'>13</var>, <var data-var='time'>13:30</var> KST Resolved - 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.

[Resolved] Temporary issue detected with Marketing feature

Jan <var data-var='date'> 7</var>, <var data-var='time'>01:30</var> KST Resolved - 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. 01. 06 22:30 ~ 2025. 01. 07 01:30 (KST) -Affected Scope: Error messages were delivered instead of responses for some customers' ALF. -Cause: Server outage on the side of the external LLM provider (OpenAI Azure). -Resolution: Switched to a different LLM provider using the same model.

Jan <var data-var='date'> 5</var>, <var data-var='time'>11:21</var> KST Resolved - The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.Jan <var data-var='date'> 5</var>, <var data-var='time'>10:24</var> KST Investigating - 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. Incident Time: January 5, 2026, 10:07 – 10:42 (KST) Affected Scope: All Front ALF–related services were affected, including 	•	ALF responses 	•	Configuration changes Cause: Database load on the ALF server, along with missing connection and request-related configurations Resolution: Server restart and resource upgrade

Jan <var data-var='date'> 5</var>, <var data-var='time'>02:30</var> KST Resolved - We identified a temporary issue affecting the Inbox and would like to share an update. The issue has now been fully resolved, and the service is operating normally. We apologize for any inconvenience caused. Incident Time: January 5, 2026, 14:26 – 14:53 (KST) Affected Scope: The following issues occurred on some channels 	•	Inbox badge not displaying correctly 	•	Inbox search unavailable 	•	Inbox-related statistics and analytics dashboards unavailable Cause: Server overload Resolution: Additional server capacity was deployed

Dec <var data-var='date'>19</var>, <var data-var='time'>16:31</var> KST Resolved - 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.Dec <var data-var='date'>19</var>, <var data-var='time'>10:26</var> KST Investigating - 수신함 기능에 일시적인 문제가 발견되어 안내드립니다. 현재 신속한 조치중이며, 복구 시 안내드리도록 하겠습니다. 이용에 불편을 드려 죄송합니다. 발견된 증상: 일부 또는 전체 고객 정보가 "알 수 없음"으로 표시됨. 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".

수신함 기능에 일시적인 문제 발견 | Temporary issue detected with Customer Support (Inbox)

Dec <var data-var='date'>19</var>, <var data-var='time'>11:02</var> KST Resolved - 안녕하세요, 채널톡입니다. 오늘 오전 약 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.Dec <var data-var='date'>19</var>, <var data-var='time'>10:50</var> KST Investigating - 현재 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.

채널톡 기능에 문제 발견 | Issue detected with Channel Talk system

Dec <var data-var='date'>19</var>, <var data-var='time'>10:59</var> KST Resolved - 상담별 통계 조회와 관련한 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 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.Dec <var data-var='date'>19</var>, <var data-var='time'>09:46</var> KST Investigating - 상담별 통계 조회에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. -발견된 증상: 기간 필터링이 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.

상담 통계에 일시적인 문제 발생 | Temporary issue detected with Analytics Feature

Dec <var data-var='date'> 5</var>, <var data-var='time'>14:23</var> KST Resolved - 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 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.)Dec <var data-var='date'> 5</var>, <var data-var='time'>14:11</var> KST Investigating - 고객 상담 화면에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. 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.

Is Channel.io down?

Channel.io status is UP

Lastest published events

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Temporary issue detected with Customer Support (Inbox)

Channel.io Services, Components and Regions

Recent Channel.io events

[Important Notice] Scheduled Maintenance for Channel.io Main DB Upgrade Preparation

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Temporary issue detected with Customer Support (Inbox)

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Get your FREE account now,
5 monitors included!

Is Channel.io down?

Channel.io status is UP

Lastest published events

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Temporary issue detected with Customer Support (Inbox)

Channel.io Services, Components and Regions

Recent Channel.io events

[Important Notice] Scheduled Maintenance for Channel.io Main DB Upgrade Preparation

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Temporary issue detected with Customer Support (Inbox)

Temporary issue detected with AI ALF feature

Temporary issue detected with AI ALF feature

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!