Mitel 장애 기록

1. 2026년 9월 3일 오후 4:29 UTCinvestigating

   우리는 유럽 연합 (EU)의 미디어에 영향을 미치는 우리의 다운스트림 제공 업체 중 하나와 문제가 있습니다. 우리는 투자하고 따라 업데이트됩니다.

2. 2026년 9월 3일 오후 8:16 UTCresolved

   다운스트림 공급자의 문제점은 이제 완전히 해결되고 우리는 더 이상 우리의 서비스 전부에 어떤 충격든지 보여줄 수 없습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 20일 오후 2:34 UTCidentified

   이 문제는 MBG를 표현하는 MSL 호스팅 대몬에 영향을 미칩니다 (독립 MBG, MiCollab, SMBC, SVI 서버). MSL 12.2 또는 12.2 MSL에 새로 생성 된 연결은 'Couldn't create 재고 보고서' 오류를 얻을 것이다. 수정은 Dev 클라우드에서 테스트됩니다. 수정이 생산에 밀어 때이 업데이트됩니다. 8/24 업데이트 - MSL의 이전 버전에서 문제가 발생했는지 확인했습니다. 수정은 테스트되고 ASAP에 게시됩니다.

2. 2026년 8월 25일 오후 2:06 UTCmonitoring

   수정은 CloudLink Daemon 버전 1.9.15의 일부로 제작되었습니다. 서버 관리자의 대몬 페이지에서 이 릴리스에 수동으로 업데이트 또는 다음 예정된 릴리스에 대한 대기는 문제를 해결해야합니다.

3. 2026년 9월 2일 오후 12:30 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 3월 24일 오전 9:23 UTCinvestigating

   We are currently experiencing an issue where the CloudLink Daemon service is down for MCX/MiCC. Our engineering team has been engaged and is actively investigating it.

2. 2026년 3월 24일 오전 10:23 UTCidentified

   Mitel Cloudlink Daemon has been rolled back to version 1.8.66+139. Please start Mitel Cloudlink Daemon service in the affected MiCC-B/MCX.

3. 2026년 3월 24일 오전 10:32 UTCmonitoring

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

4. 2026년 3월 24일 오후 1:22 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 3월 25일 오전 11:30 UTCresolved

   Root cause: The update on March 23/24 wasn’t successful and left the Windows service “Mitel CloudLink Daemon” on MiCC-B systems in a stopped state.

1. 2026년 3월 20일 오후 5:39 UTCinvestigating

   We are aware of issues in the Tunnel service and are currently investigating.

2. 2026년 3월 20일 오후 7:50 UTCidentified

   The root cause has been identified, and our team is actively working on a resolution.

3. 2026년 3월 20일 오후 10:09 UTCmonitoring

   The service has been restored and we will continue to monitor.

4. 2026년 3월 23일 오후 1:30 UTCresolved

   We experienced a temporary capacity issue that affected service availability during periods of high demand. The issue has been resolved, and additional safeguards have been put in place to prevent recurrence.

1. 2026년 3월 4일 오후 3:08 UTCinvestigating

   We are aware of an elevated error rate on the Notification service in EU and are currently investigating. At this time it appears to be impacting Workflow and Microsoft Teams presence sync. As of 10:41 EST we are seeing the services recover. We are continuing our investigation to identify the root cause.

2. 2026년 3월 4일 오후 5:36 UTCmonitoring

   Service has been restored, we will continue to monitor

3. 2026년 3월 4일 오후 9:16 UTCresolved

   The issue was caused by an unexpected, rapid spike in traffic. This surge exceeded our service capacity, resulting in a temporary service disruption.

1. 2026년 1월 21일 오후 5:28 UTCinvestigating

   We are aware of an issue affecting Mitel One on Android (version 6.9.0) where the keypad may not open during an active call, preventing DTMF input. Our team is actively working on a fix and will share updates as they become available.

2. 2026년 1월 22일 오전 11:32 UTCidentified

   The root cause has been identified, and our team is actively working on a resolution.

3. 2026년 1월 22일 오후 4:10 UTCmonitoring

   The in‑call keypad issue on Android has been fixed. Users are advised to update to Mitel One v6.9.1, now available on the Google Play Store.

4. 2026년 1월 23일 오후 7:08 UTCresolved

   The issue was caused by a recent OS compatibility change affecting the call-screen display. It has been resolved in Mitel One v6.9.1 on Android, now available on the Google Play Store.

1. 2025년 12월 16일 오전 10:51 UTCinvestigating

   We are aware of an issue affecting CloudLink Gateway containers from starting correctly. We are are actively investigating and will update as the investigation progresses.

2. 2025년 12월 16일 오전 11:11 UTCinvestigating

   The root cause has been identified and we are actively working on fix.

3. 2025년 12월 16일 오전 11:51 UTCidentified

   A new build containing the fix has been created and we are working to make this available in the public cloud, once available we will provide an update.

4. 2025년 12월 16일 오후 12:07 UTCmonitoring

   CLGW version 2.4.18 now available from the download server, for any effected gateways please restart to trigger the upgrade process. If a restart is not initiated the update will occur inline with the CLGW update schedule.

5. 2025년 12월 17일 오전 10:24 UTCresolved

   This incident has been resolved. The issue was caused by an update to the timestamp validation. Changes where implemented and this was fixed in CloudLink Gateway 2.4.18.

1. 2025년 10월 20일 오후 12:49 UTCmonitoring

   Starting at approximately 3:00 AM EST our service provider had a major outage in the US East region where our services are hosted. This impacted operations for approximately 3 hours. As of right now service has been restored and we will continue to monitor services. For more details please see here: https://health.aws.amazon.com/health/status

2. 2025년 10월 20일 오후 3:55 UTCmonitoring

   There is still some degree of instability from our service provider which is resulting in some services intermittently being impacted. While the impact does not appear to last very long it continues to happen intermittently. We remain engaged with our provider and waiting for their resolution.

3. 2025년 10월 21일 오전 2:05 UTCresolved

   Our service provider has updated that the issue is fully resolved now and we can confirm we no longer show any impact to any of our services.

1. 2025년 8월 8일 오전 10:31 UTCinvestigating

   Currently there is an issue with the authentication in the iOS version of Mitel One version 6.8.1. Please DO NOT UPGRADE to this build, a new build will be released as soon as possible that will fix this issue. A further update to this will be posted once this new build is available.

2. 2025년 8월 8일 오전 10:53 UTCidentified

   We have identified the issue and are working on a fix.

3. 2025년 8월 8일 오전 11:31 UTCmonitoring

   The fix has been released in iOS version 6.8.2 of Mitel One.

4. 2025년 8월 8일 오후 8:23 UTCresolved

   The incorrect authentication URL was mistakenly used in version 6.8.1, this was corrected in version 6.8.2.

1. 2025년 7월 7일 오후 3:18 UTCmonitoring

   Starting on Saturday July 5 there was an issue with a firewall blocking traffic to the server used to deliver automatic updates to the CloudLink Gateway and CloudLink Daemon. This would not have impacted day-to-day operations and would only be seen if you were trying to apply updates or deploy a brand new system. We identified and disabled this firewall this morning at 9:00 UTC-0400 and observed all traffic was flowing correctly again.

2. 2025년 7월 10일 오후 2:32 UTCresolved

   This incident has been resolved.

1. 2025년 4월 30일 오후 4:06 UTCinvestigating

   We are aware of an issue with presence status displaying incorrectly. The issue is currently under  investigation and we will give further updates when available.

2. 2025년 5월 22일 오후 2:09 UTCmonitoring

   A fix has been deployed with the CloudLink Gateway release 1.4.0.01-3826 or later.

3. 2025년 6월 12일 오후 2:15 UTCresolved

   This incident has been resolved. A change to the presence implementation inadvertently affected the Mitel One application and MiVO400 integration. This was fixed in the CloudLink Gateway release 1.4.0.01-3826.

1. 2025년 4월 9일 오후 2:51 UTCidentified

   We are aware of an issue with both CloudLink Gateway and CloudLink Daemon showing a pending update, but that update is not applied. We are currently working on a fix and will provide a further update when this is available. The pending update does not contain fixes for any customer reported issues, and your CloudLink connection will continue to function as normal.

2. 2025년 4월 30일 오후 3:31 UTCresolved

   This incident has been resolved.

1. 2025년 1월 16일 오후 12:22 UTCinvestigating

   We are currently investigating reports of Mitel One users not being able to log into the application. The underline issue appears to be related to the MiVO400 and is currently under investigation.

2. 2025년 1월 16일 오후 1:24 UTCmonitoring

   A fix has been deployed and we are monitoring. The fix may take some time to propagate but you can force a sync by logging into the Web Admin for your MiVO400. When successful you will see a full green dot at the top of the page.

3. 2025년 1월 17일 오후 1:10 UTCresolved

   This incident has been resolved.

1. 2024년 12월 18일 오후 6:43 UTCmonitoring

   We have identified and fixed an issue with the Twilio Social Media flow integration on MiContact Center Business where messages were very slow to be delivered. Please ensure that you do not configure the Fallback URL or Status URL in the Twilio console when configuring the Social Media flow integration. We will continue to monitor this issue and provide any updates as needed.

2. 2025년 1월 13일 오후 1:44 UTCresolved

   This incident has been resolved. Please ensure that you do not configure the Fallback URL or Status URL in the Twilio console when configuring the Social Media flow integration.

1. 2024년 9월 13일 오후 9:34 UTCidentified

   We are aware of an issue when customers send messages through the Twilio Integration configured via Mitel Administration Portal to MiContact Center Business. The messages will get routed to the agent however the agent is unable to send messages back to the customer. The agent inside of WebIgnite will see a message "Unable to send previous message." We are currently working on a fix and will provide an update once it has been deployed.

2. 2024년 9월 16일 오후 12:34 UTCmonitoring

   A fix has been deployed and the Twilio Integration should be working correctly again. We will continue to monitor for a couple days before closing this issue.

3. 2024년 9월 19일 오후 2:47 UTCresolved

   This issue has been resolved. A deployment on September 12th inadvertently impacted the Twilio integration which was subsequently fixed with a deployment on September 13th.

1. 2024년 9월 11일 오후 12:35 UTCinvestigating

   We are investigating outbound call issues from Mitel One Mobile clients with carrier minutes enabled. We will provide an update when we have more information.

2. 2024년 9월 12일 오후 2:11 UTCidentified

   We have identified the issue and are working on a fix. We will provide another update once the fix has been deployed.

3. 2024년 9월 18일 오후 1:41 UTCmonitoring

   A fix has been deployed, outbound calls should now be working properly again. We will continue to monitor and update.

4. 2024년 9월 24일 오전 11:34 UTCresolved

   This issue has been resolved. This affected a small number of customers, it was fixed with a deployment on September 17th.

1. 2024년 8월 28일 오후 2:23 UTCinvestigating

   We are currently investigating elevated error rates on the Presence service in EU region. At this time it does not appear to be affecting service but we will continue to investigate and update accordingly.

2. 2024년 9월 3일 오후 3:25 UTCmonitoring

   The Presence service in the EU region has returned to normal operation. We will continue to monitor over the next few days.

3. 2024년 9월 5일 오후 3:03 UTCresolved

   This incident has been resolved. The incident appears to be as a result of unexpected issues within the network. We are no longer seeing elevated error rates and service has been healthy for the past 5 days.

1. 2024년 8월 13일 오후 3:00 UTCidentified

   We have identified an issue where presence status from Microsoft Teams is not in sync with MiCollab. Users may notice their presence in MiCollab does not match Microsoft Teams. We are currently working on a fix and will provide an update once the fix has been deployed.

2. 2024년 8월 20일 오후 2:35 UTCresolved

   The presence status from Microsoft Teams is now correctly syncing with MiCollab again. This was caused by an issue with Microsoft Teams as acknowledged by Microsoft. It lasted from Aug 8, 2024, 8:00 p.m. EDT until Aug 15, 2024, 7:00 p.m. EDT. Please see Issue ID TM859169 in your Microsoft 365 Admin Center Service Health dashboard for more information.

1. 2024년 6월 19일 오전 3:24 UTCinvestigating

   We are receiving multiple reports of CloudLink Gateways losing connection in the AP region. Customers may receive an error message with "CLGW_ERROR_LITTLE_MOLE_FAILURE". We are currently investigating the cause.

2. 2024년 6월 19일 오전 3:42 UTCidentified

   We have identified the issue and are working on a fix.

3. 2024년 6월 19일 오전 4:03 UTCmonitoring

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

4. 2024년 6월 20일 오전 11:55 UTCresolved

   This incident has been resolved. An incorrect retention policy resulted in the container image being removed which took the service offline.

1. 2024년 3월 18일 오전 8:48 UTCinvestigating

   We are currently investigating reports of Mitel One Clients not connecting

2. 2024년 3월 18일 오전 8:48 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024년 3월 18일 오전 11:56 UTCidentified

   We have identified the issue is affecting the Media services in AP and are currently working on a fix. We will update again when the fix has been deployed.

4. 2024년 3월 18일 오후 12:46 UTCmonitoring

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

5. 2024년 3월 19일 오후 1:43 UTCresolved

   This incident has been resolved. A certificate renewal batch process failed due to the depreciation of a compute environment by our cloud provider. The compute environment has been replaced and certificates are renewing correctly again.