Aug <var data-var='date'> 7</var>, <var data-var='time'>10:32</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: August 6, 2026 19:30 ~ August 7, 2026 10:32 (KST) (approximately 15 hours 2 minutes) - Affected Scope: 154 calls across 10 channels, occurring only in calls where an agent was connected after ALF Phone Support responded first - Cause: A change in a specific processing logic of the system caused voice not to connect when a call was transferred to an agent after ALF Phone Support had responded first. - Resolution: The affected logic has been restored to its previous state, and we plan to ensure voice connects properly every time a call is transferred to an agent. Test cases for agent handoff and call transfers in ALF Phone Support have also been added to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again. Aug <var data-var='date'> 7</var>, <var data-var='time'>10:30</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.

Temporary issue detected with Phone feature

Aug <var data-var='date'> 5</var>, <var data-var='time'>08:22</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. Aug <var data-var='date'> 4</var>, <var data-var='time'>20:34</var> KST Investigating - 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.

Temporary Unavailability of CoS and Notebook for Channel Talk Default Data

Jul <var data-var='date'>30</var>, <var data-var='time'>17: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. - Incident Time: July 30, 2026 16:52:16 ~ 17:00:56 (KST) (approximately 9 minutes) - Affected Scope: Some customers using the inbox during the incident - Incident Details: 1) Inbox loading was delayed or did not complete 2) Some additional features and integration calls were not processed normally - Cause: An error occurred in a specific system setting, causing some servers to behave unintentionally, which led to failures in retrieving supplementary inbox data and, in turn, full inbox loading errors. - Resolution: The servers were restored to their previous normal state immediately after the issue was identified, resolving the disruption. We have since added checks to detect immediately when a server is not behaving as intended, and isolated failures in supplementary data retrieval so they no longer affect core inbox functionality. We will continue to strengthen monitoring to prevent similar issues from occurring again. Jul <var data-var='date'>30</var>, <var data-var='time'>16:52</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.

Temporary issue detected with Customer Support (Inbox)

Jul <var data-var='date'>20</var>, <var data-var='time'>12: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. - Incident Time: July 20, 2026 12:00 ~ July 20, 2026 16:00 (KST) (approximately 4 hours) - Affected Scope: Conversations where the automatic chat summary was not generated or was delayed upon closing - Cause: A temporary and significant slowdown in the external AI service used for summary generation caused some summaries to exceed the allowed time limit and be skipped. - Resolution: An emergency fix restored normal operation by 16:00. A structural improvement has since been deployed to run multiple AI models in parallel and use whichever completes first, ensuring summaries are generated normally even if external delays recur. We will continue to strengthen monitoring to prevent similar issues from occurring again. 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.

Jul <var data-var='date'>14</var>, <var data-var='time'>02:00</var> KST Resolved - 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. - Incident Time: July 14, 2026 02:00 ~ 10:15 (KST) (approximately 8 hours 15 minutes) - Affected Scope: Some features intermittently did not work properly across the service - Cause: A temporary network connectivity issue caused some requests to be delayed or fail to process. - Resolution: We set a time limit on request processing to prevent delays and carried out stabilization work to prevent related components from restarting unexpectedly. We have also enhanced our monitoring system to detect and respond to similar issues more quickly. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.

Jul <var data-var='date'>13</var>, <var data-var='time'>15:20</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: July 10, 2026 04:47 ~ 14:31 (KST) (approximately 9 hours 44 minutes) - Affected Scope: Channels using snippets - Cause: A styling issue caused dropdown and snippet colors to not display correctly. - Resolution: The system was restored to its previous state and the root cause has been fixed. Pre-release checks will be strengthened to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again. Jul <var data-var='date'>10</var>, <var data-var='time'>13:22</var> KST Investigating - Temporary issue has been detected with Customer Support (Inbox) Snippet feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.

Jun <var data-var='date'>24</var>, <var data-var='time'>20: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: June 24, 2026 20:48 ~ 21:23 (KST) (approximately 35 minutes) - Affected Scope: Phone feature (inbound/outbound calls) - Cause: A change in the internal data structure caused the Meet feature to stop functioning properly. - Resolution: The system has been restored to its previous state, and we will be improving our deployment process to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again. 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.

Jun <var data-var='date'>23</var>, <var data-var='time'>17: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: June 23, 2026 15:00 ~ 17:00 (KST) (approximately 2 hours) - Affected Scope: File and image messages sent by customers via KakaoTalk. - Cause: File and image messages were not properly received due to a Kakao service outage. - Resolution: The service was restored following the recovery of Kakao's service outage. Jun <var data-var='date'>23</var>, <var data-var='time'>16:11</var> KST Investigating - 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.

Temporary issue detected with Kakao Talk Integration Service

Jun <var data-var='date'>22</var>, <var data-var='time'>15:19</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: June 22, 2026 14:50 ~ 15:15 (KST) (approximately 25 minutes) - Affected Scope: All channels accessing the Channel Talk app and pages - Cause: An error occurred upon access due to a display configuration issue within the admin app. - Resolution: The affected configuration has been corrected and the service has been restored. Jun <var data-var='date'>22</var>, <var data-var='time'>15:15</var> KST Investigating - 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

Jun <var data-var='date'> 5</var>, <var data-var='time'>14: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. 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: June 5, 2026 14:34:45 ~ 14:38:30 (KST)

Temporary issue detected with AI ALF feature

May <var data-var='date'>26</var>, <var data-var='time'>15:37</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: 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. May <var data-var='date'>26</var>, <var data-var='time'>15:36</var> KST Investigating - 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. May <var data-var='date'>26</var>, <var data-var='time'>11:41</var> KST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>26</var>, <var data-var='time'>09:49</var> KST Investigating - 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.

Temporary issue detected with SMS Sending Service

May <var data-var='date'>24</var>, <var data-var='time'>05:02</var> KST Completed - The scheduled maintenance has been completed. May <var data-var='date'>24</var>, <var data-var='time'>04:42</var> KST Update - Maintenance window has been extend an hour due to unexpected delay. May <var data-var='date'>24</var>, <var data-var='time'>04:00</var> KST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>18</var>, <var data-var='time'>18:41</var> KST Update - We will be undergoing scheduled maintenance during this time. May <var data-var='date'>18</var>, <var data-var='time'>16:18</var> KST Update - We will be undergoing scheduled maintenance during this time. Apr <var data-var='date'>24</var>, <var data-var='time'>11:55</var> KST Scheduled - To enhance service stability and security, we will be performing the main database (DB) upgrade. Below are the details of the scheduled maintenance. Maintenance Schedule Date: Saturday, May 23, 2026 EDT / Sunday, May 24, 2026 KST Time: Starting at 3:00 PM EDT / 4:00 AM KST Duration: Approximately 1 hour Service Impact During the maintenance period, all Channel.io services will be unavailable. Services will be automatically resumed upon completion. Notice Document English: <a href="https://docs.channel.io/updates/en/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-260524-95ef21a3">maintenance-notice-May-24-en</a> 한국어: <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-260524-95ef21a3">maintenance-notice-May-24-ko</a> 日本語: <a href="https://docs.channel.io/updates/ja/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-260524-95ef21a3">maintenance-notice-May-24-ja</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

May <var data-var='date'>21</var>, <var data-var='time'>22: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. - Incident Time: May 21, 2026 19:00 ~ 22:00 (KST) (approximately 3 hours) - Affected Scope: Channels using messaging integrations (KakaoTalk, WeChat, etc.) and shopping mall integrations (GodoMall, ShopBy, etc.) - Incident Details: 1) Messages could not be sent through messaging apps such as KakaoTalk and WeChat 2) Order information was not saved for integrated shopping malls such as Godo Mall and ShopBy - Cause: A compatibility issue between some servers occurred during a system update. - Resolution: The affected servers were updated to restore compatibility and resolve the issue. May <var data-var='date'>21</var>, <var data-var='time'>21:08</var> KST Investigating - 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. May <var data-var='date'>21</var>, <var data-var='time'>20:55</var> KST Monitoring - We have identified the cause of the current outage and have taken corrective action. We are currently monitoring the service for stabilization. We will provide you with an update as soon as we confirm the detailed cause. We apologize for any inconvenience this may have caused. May <var data-var='date'>21</var>, <var data-var='time'>20:30</var> KST Investigating - 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.

May <var data-var='date'>18</var>, <var data-var='time'>11:37</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: May 18, 2026 10:03 ~ 11:14 (KST) (approximately 71 minutes) - Affected Scope: Delays in inbox loading, IVR response, and App Store settings screen access in some environments during the incident period - Cause: Repeated data lookup requests in App Store-related features caused a temporary surge in load on the server managing the data, which also delayed other requests using the same server. - Resolution: The processing path causing the load was temporarily disabled to restore service. Going forward, the affected processing will be separated into its own flow, and frequently used information will be stored in advance for faster access. We have also adjusted request volume and processing time to prevent similar load from accumulating again. We will continue to strengthen monitoring to prevent similar issues from occurring again. May <var data-var='date'>18</var>, <var data-var='time'>11:06</var> KST Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>18</var>, <var data-var='time'>10:32</var> KST Investigating - 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.

May <var data-var='date'>14</var>, <var data-var='time'>20:22</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: May 14, 2026, 19:47 – 20:03 (KST) Scope of Impact: Temporary unavailability of the Channel Talk admin application, including disruptions to auto-assignment and agent status updates. Cause: Temporary system overload during a deployment for product improvements. Resolution: Resolved the overload by scaling up the database servers and performing a rollback. May <var data-var='date'>14</var>, <var data-var='time'>19:56</var> KST Monitoring - We have identified the cause of the current outage and have taken corrective action. We are currently monitoring the service for stabilization. We will provide you with an update as soon as we confirm the detailed cause. We apologize for any inconvenience this may have caused. May <var data-var='date'>14</var>, <var data-var='time'>19:49</var> KST Investigating - 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.

May <var data-var='date'> 4</var>, <var data-var='time'>10: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. - 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.

Temporary issue detected with Contacts feature

Apr <var data-var='date'>27</var>, <var data-var='time'>23:45</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: April 24, 2026 15:00 ~ April 27, 2026 23:50 (KST) (approximately 3 days 8 hours 50 minutes) - Affected Scope: Channels provided with the renewed ALF analytics feature - Cause: Data from some periods was omitted from aggregation, resulting in inaccurate results being displayed - Resolution: Aggregation has been corrected to include all previously omitted data from the affected periods. Apr <var data-var='date'>24</var>, <var data-var='time'>15:00</var> KST Investigating - 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.

Temporary issue detected with AI ALF Statistics feature

Apr <var data-var='date'>26</var>, <var data-var='time'>04:19</var> KST Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>26</var>, <var data-var='time'>04:00</var> KST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Apr <var data-var='date'>24</var>, <var data-var='time'>11:56</var> KST Update - We will be undergoing scheduled maintenance during this time. Apr <var data-var='date'>24</var>, <var data-var='time'>11:55</var> KST Update - We will be undergoing scheduled maintenance during this time. Mar <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 EDT / Sunday, April 26, 2026 KST Time: Starting at 3:00 PM EDT / 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: <a href="https://docs.channel.io/updates/en/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">maintenance-notice-April-26-en</a> 한국어: <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">maintenance-notice-April-26-ko</a> 日本語: <a href="https://docs.channel.io/updates/ja/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">maintenance-notice-April-26-ja</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'>24</var>, <var data-var='time'>11:11</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-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. Apr <var data-var='date'>24</var>, <var data-var='time'>09:39</var> KST Investigating - 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.

Service Partially Unavailable

Apr <var data-var='date'>23</var>, <var data-var='time'>12:29</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: April 22, 2026 21:30 ~ April 23, 2026 12:00 (KST) (approximately 14 hours 30 minutes) - Affected Scope: User chats newly created during the incident in which tasks were triggered - Cause: A temporary disruption occurred after a change in a specific processing logic of the system - Resolution: The affected logic has been rolled back, and internal inspection procedures have been strengthened to prevent recurrence. We will continue to strengthen monitoring to prevent similar issues from occurring again. Apr <var data-var='date'>23</var>, <var data-var='time'>11:23</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.

Apr <var data-var='date'>20</var>, <var data-var='time'>11:36</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: April 20, 2026 10:25:42 ~ 11:08:41 (KST) (approximately 43 minutes) - Affected Scope: All channels 1) Some real-time chat responses were delayed compared to usual 2) The ALF Preview feature was temporarily not functioning properly - Cause: A temporary disruption occurred in some servers supporting the system under specific conditions - Resolution: Completed emergency server inspection and restoration. Preventive measures have been implemented to avoid recurrence. All systems have been fully restored to normal operation following the emergency inspection. We will continue to strengthen monitoring to prevent similar issues from occurring again. Apr <var data-var='date'>20</var>, <var data-var='time'>11:11</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.

Apr <var data-var='date'>20</var>, <var data-var='time'>10:00</var> KST Resolved - We would like to inform you of an issue where the unread message count in the inbox was inconsistent and inbox loading was slower than usual. All necessary actions have been completed, and the service is now operating normally. - Incident Details: 1) The “unread message count” displayed on the right side of the inbox did not match the actual number 2) Loading speed of the inbox list was slower than usual - Incident Time: April 20, 2026 09:55 ~ 10:39 (approximately 44 minutes) - Cause: A temporary surge in load occurred in a specific segment of the server managing inbox data - Resolution: The overloaded server segment was distributed to balance the load, and all systems have now been fully restored to normal operation.

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.

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.

Is Channel.io down?

Channel.io status is UP

Lastest published events

Temporary issue detected with Phone feature

Temporary Unavailability of CoS and Notebook for Channel Talk Default Data

Temporary issue detected with Customer Support (Inbox)

Channel.io Services, Components and Regions

Recent Channel.io events

Temporary issue detected with Phone feature

Temporary Unavailability of CoS and Notebook for Channel Talk Default Data

Temporary issue detected with Customer Support (Inbox)

Temporary issue detected with Customer Support (Inbox)

Temporary issue detected with Customer Support (Inbox)

Temporary issue detected with Customer Support (Inbox)