All Systems Operational

πŸ’¬ μ±„νŒ… | Live Chat Operational
πŸ“ž μ „ν™” | Meet Operational
πŸ“§ 이메일 | Email Operational
πŸ€– AI ALF Operational
⚑️ λΆ€κ°€ μ„œλΉ„μŠ€ | Add-ons Operational
πŸ” 연동 μ„œλΉ„μŠ€ | Integration Operational
πŸ—‚οΈ 고객 μ—°λ½μ²˜ | Contacts Operational
πŸ§‘β€πŸ’» 고객용 상담 ν™”λ©΄ | Customer Support Interface Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Dec 2, 2025

No incidents reported today.

Dec 1, 2025

No incidents reported.

Nov 30, 2025

No incidents reported.

Nov 29, 2025

No incidents reported.

Nov 28, 2025
μ „ν™” κΈ°λŠ₯에 μΌμ‹œμ μΈ 문제 λ°œμƒ | Temporary issue detected with Phone feature
Resolved - μΌμ‹œμ μΈ λ¬Έμ œκ°€ ν•΄κ²°λ˜μ—ˆμœΌλ©°, ν˜„μž¬ μ„œλΉ„μŠ€λŠ” μ •μƒν™”λ˜μ–΄ 이용이 κ°€λŠ₯함을 μ•ˆλ‚΄λ“œλ¦½λ‹ˆλ‹€. μ„œλΉ„μŠ€ μ΄μš©μ— λΆˆνŽΈμ„ λ“œλ¦° 점 μ‚¬κ³Όλ“œλ¦½λ‹ˆλ‹€.

-λ°œμƒ μ‹œκ°„: 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.
Nov 28, 11:16 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.
Nov 28, 10:47 KST
Nov 27, 2025

No incidents reported.

Nov 26, 2025

No incidents reported.

Nov 25, 2025
μ „ν™” κΈ°λŠ₯에 μΌμ‹œμ μΈ 였λ₯˜ 발견 | Temporary issue detected with Phone feature
Resolved - μΌμ‹œμ μΈ λ¬Έμ œκ°€ ν•΄κ²°λ˜μ—ˆμœΌλ©°, ν˜„μž¬ μ„œλΉ„μŠ€λŠ” μ •μƒν™”λ˜μ–΄ 이용이 κ°€λŠ₯함을 μ•ˆλ‚΄λ“œλ¦½λ‹ˆλ‹€. μ„œλΉ„μŠ€ μ΄μš©μ— λΆˆνŽΈμ„ λ“œλ¦° 점 μ‚¬κ³Όλ“œλ¦½λ‹ˆλ‹€.

λ°œμƒ μ‹œκ°„: 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.
Nov 25, 19:07 KST
Investigating - 톡화 μ’…λ£Œ μ‹œ 'μ‘λ‹΅λŒ€κΈ°μ€‘'으둜 λ³΄μ—¬μ§€λŠ” λ¬Έμ œμ™€ 이둜 인해 μ‹ κ·œ μ „ν™” μˆ˜μ‹ μ΄ λΆˆκ°€ν•œ λ¬Έμ œκ°€ λ°œκ²¬λ˜μ—ˆμŠ΅λ‹ˆλ‹€. ν˜„μž¬ 원인 ν™•μΈλ˜μ—ˆμœΌλ©° 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.
Nov 25, 17:14 KST
일본 μ „ν™” κΈ°λŠ₯ λ°œμ‹ μ— 문제 발견 | Temporary issue detected with Phone feature (JAPAN Only)
Resolved - 일본 κ΅­κ°€ 채널에 λ°œμƒν•˜λ˜ μΌμ‹œμ μΈ λ¬Έμ œκ°€ ν•΄κ²°λ˜μ—ˆμœΌλ©°, ν˜„μž¬ μ„œλΉ„μŠ€λŠ” μ •μƒν™”λ˜μ–΄ 이용이 κ°€λŠ₯함을 μ•ˆλ‚΄λ“œλ¦½λ‹ˆλ‹€. μ„œλΉ„μŠ€ μ΄μš©μ— λΆˆνŽΈμ„ λ“œλ¦° 점 μ‚¬κ³Όλ“œλ¦½λ‹ˆλ‹€.

The temporary issue has been resolved, and the service is now fully operational. We apologize for any inconvenience this may have caused.
Nov 25, 15:18 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.
Nov 25, 14:58 KST
Nov 24, 2025

No incidents reported.

Nov 23, 2025

No incidents reported.

Nov 22, 2025

No incidents reported.

Nov 21, 2025
μ „ν™” μžλ™ λ°°μ • κΈ°λŠ₯에 μΌμ‹œμ μΈ 문제 λ°œμƒ | Temporary issue detected with Meet Auto-Assignment feature
Resolved - μΌμ‹œμ μΈ λ¬Έμ œκ°€ ν•΄κ²°λ˜μ—ˆμœΌλ©°, ν˜„μž¬ μ„œλΉ„μŠ€λŠ” μ •μƒν™”λ˜μ–΄ 이용이 κ°€λŠ₯함을 μ•ˆλ‚΄λ“œλ¦½λ‹ˆλ‹€. μ„œλΉ„μŠ€ μ΄μš©μ— λΆˆνŽΈμ„ λ“œλ¦° 점 μ‚¬κ³Όλ“œλ¦½λ‹ˆλ‹€.

-λ°œμƒ μ‹œκ°„: 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.
Nov 21, 09:50 KST
Investigating - μ „ν™” μžλ™ λ°°μ • κΈ°λŠ₯에 μΌμ‹œμ μΈ λ¬Έμ œκ°€ λ°œμƒν•˜μ˜€μŠ΅λ‹ˆλ‹€. ν˜„μž¬ 원인을 νŒŒμ•… 쀑이며, λΉ λ₯΄κ²Œ 쑰치 ν›„ λ‹€μ‹œ μ•ˆλ‚΄ν•΄ λ“œλ¦¬κ² μŠ΅λ‹ˆλ‹€. μ΄μš©μ— λΆˆνŽΈμ„ λ“œλ € μ£„μ†‘ν•©λ‹ˆλ‹€.

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.
Nov 21, 09:37 KST
Nov 20, 2025

No incidents reported.

Nov 19, 2025

No incidents reported.

Nov 18, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage