Resolved -
μΌμμ μΈ λ¬Έμ κ° ν΄κ²°λμμΌλ©°, νμ¬ μλΉμ€λ μ μνλμ΄ μ΄μ©μ΄ κ°λ₯ν¨μ μλ΄λ립λλ€. μλΉμ€ μ΄μ©μ λΆνΈμ λλ¦° μ μ¬κ³Όλ립λλ€.
λ°μ μκ°: 2025. 10.01 20:00 ~ 2025. 10.10 11:50
μν₯ λ²μ: ν΄μΌ μ€μ , μ΄μ μ¬λΆ μλ λ³κ²½ μ λ°μ κ°λ₯
μμΈ: μ΄μμκ° μ μ© κ΄λ ¨ λ΄λΆ μ±λ₯ κ°μ κ³Όμ μμμ λ‘μ§ λ¬Έμ λ‘ μΈν΄ μ΄μ μκ° μλνκ° λ―Έμ μ©λ¨
μ‘°μΉ λ΄μ©: 2025λ
10μ 10μΌ 11μ 50λΆ κΈ°μ€ μ 체 μ±λ λμμΌλ‘ μ΄μμκ° μ¬κ³μ° λ° λ°μ μμ
μν μλ£
μ¬λ° λ°©μ§ λμ±
: μ¬λ° κ°λ₯ν κ·Όλ³Έμ μΈ μμΈμ κ°μ νμ¬ μ‘°μΉ μλ£νμμ΅λλ€.
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.01 20:00 ~2025.10.10 11:50 (KST)
Affected Scope: Possible occurrence when configuring holiday settings or manually changing the Chat Operation.
Cause: Due to a logic issue introduced during internal performance optimizations related to applying Chat Operation, the automation was not applied.
Resolution: As of 11:50 on October 10, 2025 (KST), we completed a full recalculation and application of Chat Operation across all channels.
Measures to Prevent Recurrence: We fixed the underlying root cause and implemented safeguards to prevent recurrence.
Oct 10, 11:50 KST
Investigating -
μ΄μμκ° μλν κΈ°λ₯μ μΌμμ μΈ λ¬Έμ κ° λ°κ²¬λμ΄ μλ΄λ립λλ€. μμλ°©νΈμΌλ‘ μλμΌλ‘ μ΄μ μνλ₯Ό λ³κ²½ ν μ μ₯ν΄μ£ΌμκΈ° λ°λλλ€. νμ¬ μ μν μ‘°μΉμ€μ΄λ©°, 볡ꡬ μ μλ΄λ리λλ‘ νκ² μ΅λλ€. μ΄μ©μ λΆνΈμ λλ € μ£μ‘ν©λλ€.
Temporary issue has been detected with Chat Operation feature. As a temporary workaround, please manually change the operating status and save. We are currently investigating the cause and will provide updates shortly. We apologize for any inconvenience this may cause.
Oct 10, 10:46 KST