Is Mitel CloudLink Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We would like to inform you that on Sunday, June 1st at 05:00 AM GMT, Unify Phone will be updated to version V3R0.97.0.The update might result in temporary service interruptions over a period of 15 minutes.Click here to view and download the release notes.

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

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.

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

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

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.

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.

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.

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

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

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

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.

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.

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.

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.

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.

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

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.

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.

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.

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

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

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

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.

This issue has been resolved. This affected a small number of customers where their presence was reverting back to an incorrect state.

The issue has been identified and we are working on a fix.

We are continuing to investigate reports on a case by case basis. If you are experiencing this issue can you please escalate through your authorized partner.

We are currently investigating reports of inconsistent presence states on Mitel One Mobile and Mitel One Web.

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.

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

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.

We are continuing to investigate this issue.

We are currently investigating reports of Mitel One Clients not connecting

This incident has been resolved. A Presence batch event fix was implemented to ensure the correct handling of endpoint events. This inadvertently caused a side affect with Presence, so was reverted back and will be addressed in a future release.

A fix has been implemented and we are monitoring the results. Please note that it is possible for certain users to be stuck in a busy state. The state will be cleared upon the next successful sent or received call.

We are currently investigating reports of users showing incorrect presence status on Mitel One Web and Mitel One Mobile for Android and iOS.

From October 27 through November 1, 2023 some customers may have not received a welcome e-mail from the platform. This has now been resolved and welcome e-mails are sending correctly. This was caused by an issue with a down stream service provider.

This incident has been resolved. A feature was implemented to inform the Mitel One Web application that active calls are no longer ringing. Since the mobile app did not handle the new notification, iOS began to take actions against the mobile app. To fix this we changed the code so it no longer affected iOS.

A fix has been deployed and we will continue to monitor. Should you continue to have issues please uninstall, then reinstall the Mitel One Mobile application and this will resolve the issue.

We have identified the issue and are currently working on a fix. This issue is not unique to iOS 17 as first reported.

We are currently investigating reports of Mitel One Mobile not notifying users of inbound calls with iOS 17, when the device is locked or the application put to the background.

This incident has been resolved.

We are aware of reported issues with Call History in the EU Region. This has been investigated and subsequently resolved. Historical Call History from October 11, 14:58 UTC to October 12, 13:44 UTC has been affected, but all new calls from October 12, 13:44 UTC will be present in Call History.

This incident has been resolved. The elevated error rate was caused by an unhandled exception in a recent update to the public cloud and that has been fixed now.

We are continuing to monitor for any further issues.

A fix has been deployed and we are no longer observing an elevated error rate. We will continue to monitor before moving this incident to Resolved.

We have identified the cause of the elevated error rates and are working on a fix.

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

This incident has been resolved.

Effective September 13, 2023, backward compatibility to versions of the CloudLink Gateway prior to version 2.3.0 will not be supported. Mitel recommends that partners upgrade their installed CloudLink Gateway customers to a minimum version of 2.3.0 to avoid service disruption on or after September 13, 2023. For more information please refer to KMS article SO7692 or use the following link: https://mitel.custhelp.com/app/answers/answer_view/a_id/1019647

This incident has been resolved. The issue was caused by a defect in the pervious version of the application which is now fixed in the 6.1.5 version currently available on the Apple App Store.

Mitel One Mobile 6.1.5 has been released for iOS devices, which contains the fix for this issue. Please update the application through the Apple App Store to apply the fix to your device.

A resolution has been developed and is currently in test.

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

We are currently investigating reports of users experiencing phantom 'Unknown' calls on Mitel One with iOS devices. Rebooting the device when you have an 'Unknown' call may alleviate further instances whilst we continue to work on a resolution.

The cause of the issue was due to errors being detected in the Customers Gateway Database for the Softphone tables which led to the Gateway restarting and not reconnecting. Not all Gateways were receiving this error hence why it did not affect everyone. Design were able to reproduce the issue by injecting those database errors in their lab environments, this allowed us to prove the fix before deploying. The fix was to be more robust to those database errors.

A fix for the issue has been deployed earlier today and we continue to monitor. For gateways that have been affected by this issue, rebooting the gateway will ensure the fix is automatically downloaded and installed. (This may take up to 20 minutes) Remaining gateways will be upgraded in line with the Auto Update Schedule if enabled on the CloudLink Account. If you are still experiencing issues after the reboot or Auto Update, then please contact Mitel via TechCentral Tracker so we can investigate further.

We continue to investigate each report on an individual basis and still require customers that are experiencing the issue to contact Mitel via our Tech Central Tracker. We have identified an issue that we believe is the underlying root cause and are currently working on a resolution. Recovering Gateways in this condition would still need assistance from Mitel Product Support and we will require remote access to do so.

We have seen a small increase in the influx of tickets stating the CloudLink Gateways are reporting connection issues and we are continuing to investigate these reports on an individual basis. If your customer experiences issues with the CloudLink Gateway not connecting, then please do not factory reset as this could result in further issues. Please contact Mitel via TechCentral Tracker to assist us in identifying the issue and any trends. We will offer a further update if an underlying issue is detected and will also offer method of recovery.

We are no longer seeing any issues and service has been healthy for the past 30 minutes. Confirmed with our downstream provider that there was an interruption to service that impacted the CDN we use to cache the web applications, and the impact lasted for approximately 40 minutes between 9:37 AM and 10:13 AM PDT.

Our downstream provider has updated that service is being restored and we can see that our web applications are now responding again. We have seen stable service for the past 15 minutes so we are moving this incident to monitoring.

We are aware of issues with our downstream provider impacting service to our US cloud. We are currently engaged and working on resolution and will provide further updates when we have more details. The issue appears to be isolated to web applications while our REST APIs are still working, but we will continue to monitor while our downstream provider is working on this issue.

An unexpected interruption to service caused some CloudLink Gateways to lose connection to the cloud for approximately 2 hours. The connection was recovered and the gateways automatically reconnected to the cloud.

This incident has been resolved.

Service has been restored. Any sites that have not reconnected should reconnect automatically. We will continue to monitor over the next few hours.

We continue to work on restoring service.

While we continue to work on recovery we have observed that the impact is wider than initially observed affecting all applications that use Media Services in the AP cloud. This now impacts call services on Mitel One, MiTeam Meetings, and Voice Assist on the AP cloud.

We have identified the issue to be with the underlying caching layer in the CloudLink Media Services stack and are working to recover service as quickly as possible.

We are aware of an issue impacting Voice Assist on the AP cloud. The Voice Assist feature is not currently working and you may see a message indicating the SIP registration has failed. We are investigating and will update as soon as we have more information.

This incident has been resolved.

Our downstream provider has updated that service is being restored and we can see that our API's are now responding again. We have seen stable service for the past 15 minutes so we are moving this incident to monitoring.

We're still getting regular updates from our downstream provider that they are working to resolve the issue, but service has not yet been restored. We continue to monitor.

All applications running on our US cloud will not be able to authenticate or make API calls to the platform. Our downstream provider has acknowledged the issue and is working to resolve as quickly as they can.

We are aware of issues with our downstream provider impacting service to our US cloud. We are currently engaged and working on resolution and will provide further updates when we have more details.

An unexpected interruption to service caused some CloudLink Gateways to briefly lose connection to the cloud. The automatic recovery function worked as designed and the gateways automatically reconnected to the cloud within a few minutes.

This incident has been resolved.

This update has been delivered as of 17th of May 2023.

There is an increase in RTP/SRTP capacity in CloudLink which will be made available within 60 days of this notice. It is recommended that customer update their network security systems to allow for the increase in traffic capacity prior to the go live date. The planned date to increase the port range is the 16th of May 2023. Old port range: 16384 – 32768 New port range: 16384 – 49152 For more details please refer to KMS article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1018987

A small number of attempts to start a new call failed due to an incorrectly configured infrastructure scaling event. This issue was resolved through a manual scale up of the media services infrastructure.

This incident has been resolved. This issue was caused by an update to schema validation on CloudLink Admin API.

We've implemented a fix for this issue, and verified that new users can be created for CloudLink enabled MiCollab installations.

We're currently aware of an issue causing failures creating users for CloudLink enabled MiCollab installations, and are working toward a resolution.

This incident has been resolved. This issue was caused by an underlying caching layer in the CloudLink Media Services stack.

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

We've identified the issue and are currently working towards a resolution

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating reports of calls not being possible.

This continues to remain in effect. This notice has been in place at the top of the status page for over a year now and no longer needs to be at the top so it will be moved to Incident History.

Users within the Russian Federation, and Belarus will be unable to use any Cloudlink enabled applications or third-party integrations at this time.

This incident has been resolved.

We have published version 2.2.2 for the CloudLink Gateway. Please update the CloudLink Gateway to update to this new version.

We have published version 2.2.1 for the CloudLink Gateway. Please update the CloudLink Gateway to update to this new version.

We are aware of an issue affecting the CloudLink Gateway where it loses its connection with the cloud. This issue only affects the physical hardware appliance. Symptoms of this issue include calls in applications failing to connect, or presence status failing to update. If you encounter this scenario, please restart (power cycle) the CloudLink Gateway. We are working on a permanent fix. Please watch this incident for further updates. For more information please refer to KMS article https://mitel.custhelp.com/app/answers/answer_view/a_id/1019017

This incident has been resolved.

Please be aware that we have recognized that Mitel One Mobile is no longer found on the Google App Store. At this time, we are working with the Google Store to understand why it is currently unavailable and will report back once more information becomes available. This does not affect iOS devices

This incident has been resolved.

We are still waiting for a fix from our downstream provider. They are still working on it and do not have an ETA for resolution, so we will continue to monitor and update accordingly.

We have identified the issue is with our downstream provider, and they have acknowledged and are working on it.

We are currently investigating issues with joining meetings on MiTeam Meetings

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We're currently investigating an issue with Authentication in all clouds, this will affect all Cloudlink services

This incident has been resolved.

The downstream cloud provider has marked the issue as resolved and we are seeing return to normal operation.

We're currently seeing a higher than normal error rate when accessing Cloudlink web applications such as Mitel One, MiTeam Meetings, and portals. This is caused by a downstream cloud provider issue. We are monitoring for resolution.

This incident has been resolved.

This issue has been resolved. You may be required to refresh your browser page or re-launch your mobile/desktop application in order to restore functionality.

We're currently investigating an error sending chat messages in the US

This incident has been resolved.

We have implemented a fix for all regions and testing shows everything working. Please note that there may be some caching occurring so if you encounter an error please wait a minute and try again. You may need to quit and restart any applications that have been open during this event. We will continue to monitor for the next few hours.

We are continuing to work on a fix for this issue.

We have identified the issue and are working on a fix now. This issue affects all users authenticating with the CloudLink platform. Some users may see it working now while others may not. Will update again once we confirm it is working for all users.

We are also seeing a higher error rate in the US region.

We're currently investigating a higher than normal error rate with the authentication service in the EU region.

This incident has been resolved.

A fix has been implemented. You may need to clear your browser cache for accounts.mitel.io and log in before accounts load correctly.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently investigating reports with the Accounts Console not being able to fetch account information.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We're currently investigating an issue with MiCC chats being delivered to incorrect queues.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We're currently investigating an issue with chat attachments in all regions (US, EU, and AP)

This incident has been resolved.

We are continuing to monitor for any further issues.

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

We have received multiple reports of MiTeam Meetings Calendar integration not loading meetings scheduled in the future. We've found the issue and are currently testing a fix. Signing out of then back in to the Calendar integration on the Calendar tab of the settings in the Meetings application will load future meetings.

We've found the issue and are currently testing a fix.

Outbound SMS traffic has stabilized and the issue has been resolved

The issue has been resolved on the remote host and we will be monitoring the traffic for the next couple of hours

SMS provider has identified partial outage with their number provider for message routing and are currently working with their upstream partner to resolve issue. Customer may see message rejections or submission delays for outbound messages

We have identified partial failure of our outbound SMS service that is affecting less than 5% of our traffic. We are currently working with our upstream provider to identify the issue

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue. Joining meetings via the web, mobile, or desktop clients remains unaffected.

We're currently investigating reports of failures to dial into MiTeam Meetings via PSTN.

This incident has been resolved.

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

We have identified the problem and are working on a fix, will update once the fix has been pushed to production.

We are currently investigating reports of incorrect inbound caller information being displayed.

This incident has been resolved.

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

We are aware of an issue that is affecting logins in all regions. If you are already logged in, applications should continue to function normally, but if you need to log in you will be presented with an error and you won't be able to log in. We are actively working on correcting the issue.

This incident has been resolved.

We have fixed this issue and calls should be working again. We will continue to monitor for the next couple of hours.

We have identified an issue where a small number of calls are failing in our EU cloud. The issue is isolated to a single instance in the cluster and only some customers may see the issue. We are actively working on a fix.

This incident has been resolved. The underlying cause of this issue was the cluster hit capacity limit and did not scale up. We corrected the issue and the cluster scaled up to handle additional capacity correctly.

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

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

We're currently investigating reports of calls failing in the EU cloud.

The service continues to operate as expected and all SMS traffic has been stable and fully operational

There have been no further message rejection events for for over 4 hours. We are awaiting confirmation that the issue has been resolved from our service provider and will continue to monitor

Our service provider has identified that intermittent failures with their external number resolution (ENUM) service is resulting in an increase in rejected MT(outbound) messages They are currently working with their ENUM partner engineering to resolve the issue. We apologize for any inconvenience this may be causing, and will provide information as it becomes available.

We are currently experiencing intermittent rejection of outbound SMS messages from our service provider. The issue has been escalated with our provider and will updates as we continue to investigate the issue.

The fix has been deployed to Mitel One app and all issues are resolved. We will continue to monitor to ensure applications are fully functional with no remaining issues.

The issue has been identified and a fix has been delivered to MiTeam Meetings. A fix for Mitel One application is scheduled to be applied tomorrow morning Thursday January 6. We will continue to monitor the fix on meetings and update the incident on the delivery to Mitel One

The following issues have been reported based on the update Jan 4th 2022: - The Chrome 97+ user will lose the connection to the meeting and be reconnected if any user (regardless of browser/app) performs one of the following actions: Stop video, Start video, Join meeting, Leave meeting, Changing your camera setting, Start or Stop screen sharing - During the reconnect, the Chrome 97 user will see these messages: Connection lost, reconnecting … (yellow) followed by reconnected (green) - After being reconnected, the Chrome 97 user's own video tile (self tile) may be grey or have the user's avatar, but the camera will still be enabled if it was enabled prior to the reconnect event. Important: If your camera light is on and if the control bar says 'Stop video' then you are still sending video into the meeting. We apologize for any inconvenience and are working on resolving the issue, and will provide an update as early as possible

This incident has been resolved.

Our provider has restored service on the west coast and we are seeing recovery. Will continue to monitor over the next hour.

Confirmed with our provider that there is an ongoing networking issue on the west coast and users will be impacted. We are working with our provider to resolve this issue and will update when we have more information.

We are receiving reports that some users are unable to use MiTeam Meetings or Mitel One in North America. At this time it appears to be isolated to users on the west coast, but we are investigating and will update as soon as we have more information.

This incident has been resolved.

We have confirmed that service has been restored at our downstream provider and we are seeing our services returning to normal operation. We will keep this incident in monitoring as we continue to observe our services.

We are continuing to work with our downstream provider on resolution but service remains impacted while they work on this issue.

Confirmed with downstream provider that there is an issue on their end that is affecting the US East region which is impacting our service. Will continue to work with our provider to resolve this issue and provide updates when available.

We are observing a high error rate from multiple services at this time that appears to be caused by our downstream provider. We are working with the provider to identify the issue.