Channel.io incident

Service Partially Unavailable

Resolved after 11 hours 54 minutes, on March 4, 2026.

resolved Mar 05, 2026, 11:38 AM UTC

The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: 2026. 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.

Started
Mar 04, 2026, 11:30 PM UTC
Resolved
Mar 05, 2026, 11:24 AM UTC
Duration
11h 54m
Detected by Pingoru
Mar 04, 2026, 11:30 PM UTC

Update timeline

  1. resolved Mar 05, 2026, 11:38 AM UTC

    The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused. - Incident Time: 2026. 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.

Your product runs on more than Channel.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →