Istoricul incidentelor Channelio

1. 1 septembrie 2026 la 06:02 UTCinvestigating

   A fost detectată o problemă temporară cu funcţia de Asistenţă Clienţi (Inbox). În prezent investigăm cauza și vom oferi actualizări în scurt timp. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza.

2. 1 septembrie 2026 la 07:37 UTCresolved

   Problema temporară a fost rezolvată, iar serviciul este acum pe deplin operațional. Ne cerem scuze pentru orice neplăceri cauzate. - Timpul incidentului: 31 august 2026 20:00 ~ 1 septembrie 2026 16:00 (KST) (aproximativ 20 ore) - Domeniul de aplicare afectat: canale care utilizează caracteristici programate, cum ar fi modificări de stare de consultare și trimiterea de e-mail follow-up - Detalii incident: 1) Modificările stadiului consultării programate nu au fost prelucrate corect 2) E-mailurile ulterioare nu au fost trimise corect 3) Alte sarcini programate nu au fost prelucrate corect - Cauza: In timpul lucrarii de imbunatatire a serviciilor, unele servere s-au comportat neintenţionat, determinând ca sarcinile programate sa fie inregistrate ca completate chiar daca acestea nu au fost de fapt prelucrate, ceea ce a prevenit retries automate. - Rezolutie: La identificarea problemei, am luat masuri imediate pentru a ne asigura ca sarcinile sunt procesate corect, imbunatatite sistemul astfel incat sarcinile sa fie marcate doar o data terminate, si sa adaugam detectia imediata pentru comportamentul anormal al serverului. Vom continua să consolidăm monitorizarea pentru a preveni repetarea unor probleme similare.

Traducere automată din actualizarea oficială a incidentului.

1. 1 septembrie 2026 la 05:02 UTCinvestigating

   A fost detectată o problemă temporară cu funcţia de marketing. În prezent investigăm cauza și vom oferi actualizări în scurt timp. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza.

2. 1 septembrie 2026 la 07:37 UTCresolved

   Problema temporară a fost rezolvată, iar serviciul este acum pe deplin operațional. Ne cerem scuze pentru orice neplăceri cauzate. - Timpul incidentului: 31 august 2026 20:00 ~ 1 septembrie 2026 16:00 (KST) (aproximativ 20 ore) - Domeniul de aplicare afectat: Canale care au trimis mesaje de marketing - Detalii incident: 1) Campaniile au fost trimise doar unor destinatari destinaţi 2) Unele mesaje o singură dată (OTM) nu a reușit să trimită - Cauza: In timpul lucrarii de imbunatatire a serviciilor, unele servere s-au comportat neintenţionat, determinând ca sarcinile programate sa fie inregistrate ca completate chiar daca acestea nu au fost de fapt prelucrate, ceea ce a prevenit retries automate. - Rezolutie: La identificarea problemei, am luat masuri imediate pentru a ne asigura ca sarcinile sunt procesate corect, imbunatatite sistemul astfel incat sarcinile sa fie marcate doar o data terminate, si sa adaugam detectia imediata pentru comportamentul anormal al serverului. Vom continua să consolidăm monitorizarea pentru a preveni repetarea unor probleme similare.

Traducere automată din actualizarea oficială a incidentului.

1. 7 august 2026 la 01:30 UTCinvestigating

   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. 7 august 2026 la 01:41 UTCresolved

   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.

1. 4 august 2026 la 11:34 UTCinvestigating

   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. 4 august 2026 la 23:22 UTCresolved

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

1. 30 iulie 2026 la 08:02 UTCinvestigating

   A fost detectată o problemă temporară cu funcţia de Asistenţă Clienţi (Inbox). În prezent investigăm cauza și vom oferi actualizări în scurt timp. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza.

2. 30 iulie 2026 la 08:04 UTCresolved

   Problema temporară a fost rezolvată, iar serviciul este acum pe deplin operațional. Ne cerem scuze pentru orice neplăceri cauzate. - Timpul incidentului: 30 iulie 2026 16:52:16 ~ 17:00:56 (KST) (aproximativ 9 minute) - Domeniul de aplicare afectat: Unii clienti folosesc inbox-ul in timpul incidentului - Detalii incident: 1) Încărcarea inbox a fost amânată sau nu a fost finalizată 2) Unele caracteristici suplimentare și apeluri de integrare nu au fost prelucrate în mod normal - Cauza: O eroare a apărut într-o anumită setare de sistem, provocând unele servere să se comporte involuntar, ceea ce a dus la eșecuri în recuperarea datelor suplimentare inbox și, la rândul său, erori complete de încărcare inbox. - Rezoluţie: Serverele au fost restaurate în starea lor normală anterioară imediat după identificarea problemei, soluţionând perturbarea. De atunci am adăugat controale pentru a detecta imediat când un server nu se comportă așa cum se intenționează, și eșecuri izolate în recuperarea de date suplimentare, astfel încât acestea să nu mai afecteze funcționalitatea inbox de bază. Vom continua să consolidăm monitorizarea pentru a preveni repetarea unor probleme similare.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 03:06 UTCresolved

   Problema temporară a fost rezolvată, iar serviciul este acum pe deplin operațional. Ne cerem scuze pentru orice neplăceri cauzate. - Timpul incidentului: 20 iulie 2026 12:00 ~ 20 iulie 2026 16:00 (KST) (aproximativ 4 ore) - Domeniul de aplicare afectat: Conversații în cazul în care rezumatul automat de chat nu a fost generat sau a fost întârziat la închidere - Cauza: O încetinire temporară și semnificativă în serviciul extern AI utilizat pentru generarea sumar a cauzat unele rezumate pentru a depăși limita de timp permisă și să fie omis. - Rezoluţie: o reparaţie de urgenţă restaurată până la 16:00. De atunci, a fost implementată o îmbunătățire structurală pentru a rula în paralel mai multe modele AI și a utiliza oricare dintre acestea se completează mai întâi, asigurându-se că rezumatele sunt generate în mod normal, chiar dacă întârzierile externe reapar. Vom continua să consolidăm monitorizarea pentru a preveni repetarea unor probleme similare. A fost detectată o problemă temporară cu funcţia de Asistenţă Clienţi (Inbox). În prezent investigăm cauza și vom oferi actualizări în scurt timp. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 09:05 UTCresolved

   A fost detectată o problemă temporară cu funcţia de Asistenţă Clienţi (Inbox). În prezent investigăm cauza și vom oferi actualizări în scurt timp. Ne cerem scuze pentru orice neplăceri pe care le-ar putea cauza. - Timpul incidentului: 14 iulie 2026 02:00 ~ 10:15 (KST) (aproximativ 8 ore 15 minute) - Domeniul de aplicare afectat: Unele caracteristici intermitent nu au funcţionat corect în cadrul serviciului Cauza: O problemă temporară de conectivitate la rețea a cauzat întârzierea unor cereri sau incapacitatea de a procesa. - Rezoluţie: Am stabilit un termen limită la procesarea cererii pentru a preveni întârzierile şi a efectua lucrările de stabilizare pentru a preveni repornirea neaşteptată a componentelor conexe. De asemenea, am îmbunătățit sistemul nostru de monitorizare pentru a detecta și a răspunde mai rapid la probleme similare. Problema temporară a fost rezolvată, iar serviciul este acum pe deplin operațional. Ne cerem scuze pentru orice neplăceri cauzate.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 04:22 UTCinvestigating

   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.

2. 13 iulie 2026 la 06:20 UTCresolved

   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.

1. 24 iunie 2026 la 13:00 UTCresolved

   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.

1. 23 iunie 2026 la 07:11 UTCinvestigating

   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. 23 iunie 2026 la 08:16 UTCresolved

   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.

1. 22 iunie 2026 la 06:15 UTCinvestigating

   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. 22 iunie 2026 la 06:19 UTCresolved

   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.

1. 5 iunie 2026 la 05:49 UTCresolved

   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)

1. 26 mai 2026 la 02:41 UTCmonitoring

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

2. 26 mai 2026 la 06:36 UTCinvestigating

   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.

3. 26 mai 2026 la 06:37 UTCresolved

   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.

1. 21 mai 2026 la 11:55 UTCmonitoring

   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.

2. 21 mai 2026 la 12:08 UTCinvestigating

   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.

3. 21 mai 2026 la 13:02 UTCresolved

   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.

1. 18 mai 2026 la 01:32 UTCinvestigating

   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. 18 mai 2026 la 02:06 UTCmonitoring

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

3. 18 mai 2026 la 02:37 UTCresolved

   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.

1. 14 mai 2026 la 10:49 UTCinvestigating

   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. 14 mai 2026 la 10:56 UTCmonitoring

   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.

3. 14 mai 2026 la 11:22 UTCresolved

   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.

1. 4 mai 2026 la 08:56 UTCresolved

   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.

1. 27 aprilie 2026 la 08:50 UTCinvestigating

   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. 28 aprilie 2026 la 06:19 UTCresolved

   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.

1. 24 aprilie 2026 la 00:39 UTCinvestigating

   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. 24 aprilie 2026 la 02:11 UTCresolved

   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.

1. 23 aprilie 2026 la 02:23 UTCinvestigating

   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.

2. 23 aprilie 2026 la 03:29 UTCresolved

   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.