Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Störungsverlauf von Mitel

    52 Mitel incidents · Februar 2022 — official updates, affected components, duration and resolution details.

    Zurück zum aktuellen Status

    Medienverzögerungen in der EU

    Beginn 3. September 2026 um 16:29 UTC · 3h 47m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Media
    1. 3. September 2026 um 16:29 UTCinvestigating

      Uns ist ein Problem mit einem unserer nachgelagerten Anbieter bekannt, das Medien in der EU betrifft. Wir untersuchen und werden entsprechend aktualisieren.

    2. 3. September 2026 um 20:16 UTCresolved

      Das Problem mit dem nachgelagerten Anbieter ist jetzt vollständig gelöst und wir können bestätigen, dass wir keine Auswirkungen mehr auf unsere Dienste zeigen.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    CloudLink Daemon - Neu eingerichtete Verbindungen für den Daemon-Fehler "Inventarbericht nicht erstellen"

    Beginn 20. August 2026 um 14:34 UTC · 12d 21h

    Pending
    Betroffene Komponenten
    CloudLink Accounts Portal
    1. 20. August 2026 um 14:34 UTCidentified

      Dieses Problem betrifft jeden MSL-gehosteten Daemon, der ein MBG als Teil des Manifests hat (stand-alone MBG, MiCollab, SMBC, SVI Server). Alle neu erstellten Verbindungen auf MSL 12.2 oder Upgrades auf 12.2 MSL erhalten den Fehler "Inventarbericht nicht erstellen" . Ein Fix wird in unserer Dev Cloud getestet. Dies wird aktualisiert, wenn der Fix in die Produktion gebracht wird. Update 8/24 - Wir haben Berichte bestätigt, dass das Problem bei älteren Versionen von MSL auftritt. Der Fix wird getestet und wird so schnell wie möglich veröffentlicht.

    2. 25. August 2026 um 14:06 UTCmonitoring

      Der Fix wurde als Teil von CloudLink Daemon Version 1.9.15 in Produktion genommen. Wenn Sie manuell von der Daemon-Seite im Server-Manager auf diese Version aktualisieren oder auf die nächste geplante Version warten, wird das Problem behoben.

    3. 2. September 2026 um 12:30 UTCresolved

      Dieser Vorfall wurde als behoben bestätigt.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    CloudLink Daemon Service Disruption for MCX/MiCC

    Beginn 24. März 2026 um 09:23 UTC · 1d 2h

    OutageKritischer Vorfall
    Betroffene Komponenten
    Tunnel
    1. 24. März 2026 um 09: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. 24. März 2026 um 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. 24. März 2026 um 10:32 UTCmonitoring

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

    4. 24. März 2026 um 13:22 UTCmonitoring

      We are continuing to monitor for any further issues.

    5. 25. März 2026 um 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.

    Issue with Tunnel service causing connection errors

    Beginn 20. März 2026 um 17:39 UTC · 2d 19h

    OutageKritischer Vorfall
    Betroffene Komponenten
    Tunnel
    1. 20. März 2026 um 17:39 UTCinvestigating

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

    2. 20. März 2026 um 19:50 UTCidentified

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

    3. 20. März 2026 um 22:09 UTCmonitoring

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

    4. 23. März 2026 um 13: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.

    Elevated Error Rate on Notification Service in EU

    Beginn 4. März 2026 um 15:08 UTC · 6h 8m

    OutageKritischer Vorfall
    Betroffene Komponenten
    Notifications
    1. 4. März 2026 um 15: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. 4. März 2026 um 17:36 UTCmonitoring

      Service has been restored, we will continue to monitor

    3. 4. März 2026 um 21: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.

    An issue in Mitel One v6.9.0 on Android prevents keypad access during active calls.

    Beginn 21. Januar 2026 um 17:28 UTC · 2d 1h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Mitel One
    1. 21. Januar 2026 um 17: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. 22. Januar 2026 um 11:32 UTCidentified

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

    3. 22. Januar 2026 um 16: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. 23. Januar 2026 um 19: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.

    Issue with CloudLink Gateway - Containers could not be started

    Beginn 16. Dezember 2025 um 10:51 UTC · 23h 34m

    OutageKritischer Vorfall
    Betroffene Komponenten
    CloudLink Gateway PortalMitel One
    1. 16. Dezember 2025 um 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. 16. Dezember 2025 um 11:11 UTCinvestigating

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

    3. 16. Dezember 2025 um 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. 16. Dezember 2025 um 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. 17. Dezember 2025 um 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.

    Major Outage at Service Provider in US East Region

    Beginn 20. Oktober 2025 um 12:49 UTC · 13h 16m

    Pending
    Betroffene Komponenten
    Admin
    1. 20. Oktober 2025 um 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. 20. Oktober 2025 um 15: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. 21. Oktober 2025 um 02: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.

    Unable to log in to Mitel One Mobile on iOS after upgrading to 6.8.1

    Beginn 8. August 2025 um 10:31 UTC · 9h 51m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    Mitel One
    1. 8. August 2025 um 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. 8. August 2025 um 10:53 UTCidentified

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

    3. 8. August 2025 um 11:31 UTCmonitoring

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

    4. 8. August 2025 um 20:23 UTCresolved

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

    CloudLink Gateway Automatic Updates

    Beginn 7. Juli 2025 um 15:18 UTC · 2d 23h

    Pending
    1. 7. Juli 2025 um 15: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. 10. Juli 2025 um 14:32 UTCresolved

      This incident has been resolved.

    CloudLink Presence Status Issues

    Beginn 30. April 2025 um 16:06 UTC · 42d 22h

    Pending
    1. 30. April 2025 um 16: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. 22. Mai 2025 um 14:09 UTCmonitoring

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

    3. 12. Juni 2025 um 14: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.

    CloudLink Gateway and CloudLink Daemon Pending Update

    Beginn 9. April 2025 um 14:30 UTC · 21d 1h

    Pending
    Betroffene Komponenten
    CloudLink Gateway Portal
    1. 9. April 2025 um 14: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. 30. April 2025 um 15:31 UTCresolved

      This incident has been resolved.

    Mitel One users not able to log into the application.

    Beginn 16. Januar 2025 um 12:22 UTC · 1d 0h

    Pending
    Betroffene Komponenten
    Mitel One
    1. 16. Januar 2025 um 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. 16. Januar 2025 um 13: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. 17. Januar 2025 um 13:10 UTCresolved

      This incident has been resolved.

    MiContact Center Business Chat Message Delays

    Beginn 18. Dezember 2024 um 18:43 UTC · 25d 19h

    Pending
    Betroffene Komponenten
    WorkflowWorkflowWorkflow
    1. 18. Dezember 2024 um 18: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. 13. Januar 2025 um 13: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.

    Twilio Integration on MiContact Center Business

    Beginn 13. September 2024 um 21:34 UTC · 5d 17h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    WorkflowWorkflowWorkflow
    1. 13. September 2024 um 21: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. 16. September 2024 um 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. 19. September 2024 um 14: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.

    Mitel One Mobile One-Way Audio in EU Region

    Beginn 11. September 2024 um 12:35 UTC · 12d 22h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Media
    1. 11. September 2024 um 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. 12. September 2024 um 14: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. 18. September 2024 um 13:41 UTCmonitoring

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

    4. 24. September 2024 um 11:34 UTCresolved

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

    Elevated Error Rates in EU Region

    Beginn 28. August 2024 um 14:23 UTC · 8d 0h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Presence
    1. 28. August 2024 um 14: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. 3. September 2024 um 15: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. 5. September 2024 um 15: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.

    Microsoft Teams to MiCollab Presence Out of Sync

    Beginn 13. August 2024 um 15:00 UTC · 6d 23h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    WorkflowWorkflowWorkflow
    1. 13. August 2024 um 15: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. 20. August 2024 um 14: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.

    CloudLink Gateways Unavailable in AP Region

    Beginn 19. Juni 2024 um 03:24 UTC · 1d 8h

    OutageKritischer Vorfall
    Betroffene Komponenten
    Tunnel
    1. 19. Juni 2024 um 03: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. 19. Juni 2024 um 03:42 UTCidentified

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

    3. 19. Juni 2024 um 04:03 UTCmonitoring

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

    4. 20. Juni 2024 um 11:55 UTCresolved

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

    Mitel One Clients not connecting in AP

    Beginn 18. März 2024 um 08:48 UTC · 1d 4h

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    Media
    1. 18. März 2024 um 08:48 UTCinvestigating

      We are currently investigating reports of Mitel One Clients not connecting

    2. 18. März 2024 um 08:48 UTCinvestigating

      We are continuing to investigate this issue.

    3. 18. März 2024 um 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. 18. März 2024 um 12:46 UTCmonitoring

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

    5. 19. März 2024 um 13: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.