Channel.io had 36 outages in the last 2 years totaling 1201h 42m of downtime — averaging 1.5 incidents per month.
There were 36 Channel.io outages since July 28, 2025 totaling 1201h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 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.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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.
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.
The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.
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.
A fix has been implemented and we are monitoring the results.
The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.
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 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.
The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.
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.
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.
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.
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.
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: 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.
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.
수신함 기능에 일시적인 문제가 발견되어 안내드립니다. 현재 신속한 조치중이며, 복구 시 안내드리도록 하겠습니다. 이용에 불편을 드려 죄송합니다. 발견된 증상: 일부 또는 전체 고객 정보가 "알 수 없음"으로 표시됨. 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".
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.
상담별 통계 조회에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. -발견된 증상: 기간 필터링이 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 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.
전화 기능에 일시적인 문제가 발생하였습니다. 현재 원인을 파악 중이며, 빠르게 조치 후 다시 안내해 드리겠습니다. 이용에 불편을 드려 죄송합니다. 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.
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 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.
통화 종료 시 '응답대기중'으로 보여지는 문제와 이로 인해 신규 전화 수신이 불가한 문제가 발견되었습니다. 현재 원인 확인되었으며 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.
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 발생 시간: 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.
일본 국가 채널의 전화 기능 발신에 문제가 발견되었습니다. 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.
일본 국가 채널에 발생하던 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 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 Meet Auto-Assignment feature. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 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.
전화 수신시 일부 채널에서 연결 불가, 지연이 되는 상황이 발생하였습니다. 현재 서비스는 정상화 되어 이용이 가능함을 안내드립니다. 이용에 불편을 드려 죄송합니다. 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.
트윌리오 계정을 사용해 해외 고객에게 발송되는 문자 (마케팅, 팔로업 알림) 발송에 일시적인 문제가 발견되었습니다. 트윌리오 측 장애로 확인되며, 불편을 드려 죄송합니다. 자세한 내용은 트윌리오 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/
We are continuing to investigate this issue.
트윌리오 서비스의 일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. 자세한 내용은 트윌리오 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/
수신함에서 10월 15일 오전 11시~10월 19일 오후 12시 45분 작성된 메시지에 대해 검색이 불가능한 문제가 발견되었습니다. 원인 확인 후 해결 중입니다. 불편을 드려 죄송합니다. 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.
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다. -발생 시간: 2025. 10. 15 11:15 ~ 2025. 10. 20 11:32 (KST) -영향 범위: 신규 작성된 메시지가 검색되지 않음 -원인: 메시지 검색을 위한 데이터베이스의 최대 용량 초과로 인해 신규 데이터 적재 실패 -조치 내용: 메시지 검색용 DB 용량 증설 및 유실된 기간의 메시지를 다시 적재 -재발 방지 대책: 적재 용량 관련 모니터링 알람 추가 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.10.1511:15 ~2025.10.2011:32 (KST) -Affected Scope: Newly created messages were not searchable. -Cause: New data ingestion failed because the database used for message search exceeded its maximum capacity. -Resolution: Increased the capacity of the message-search database and re-ingested messages for the affected period. -Measures to Prevent Recurrence: Added monitoring alerts related to ingestion capacity.
진행 중 상담에 전화 유형의 상담이 없으나, 오퍼레이터 상태가 '전화 후처리 중'으로 표시되는 문제가 일부 케이스에서 아직 해결되지 않은 것으로 확인됩니다. 문제 해결 후 재배포를 진행할 예정입니다. 불편을 드려 죄송합니다. 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.
일시적인 문제가 해결되었으며, 현재 서비스는 정상화되어 이용이 가능함을 안내드립니다. 서비스 이용에 불편을 드린 점 사과드립니다 The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.