Is Level365 down?

We have identified an issue causing some users to be unable to log in to the Level365 Softphone applications. For desktop applications, please install the newest version by following this link: Softphone for Desktop We are still actively working towards a resolution allowing mobile application logins.

We are monitoring an issue causing some users to be unable to log in to the Level365 Softphone applications. We have pushed a new version update to resolve this issue. For desktop applications, please install the newest version by following this link: Softphone for Desktop The new Android version has been released to the Play Store and can now be updated on devices. Apple approval for iOS devices is still pending and we will provide an update once the app is approved.

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

We have deployed a fix that restores login for all versions of the Level365 Softphone (Desktop and Mobile). To log in, fully close the application and relaunch it. - Desktop (standard install): After relaunching, the app will update to the latest version automatically. - Desktop (MSI install): After relaunching, you can log in on your current version. The new version does not update automatically; your administrator will need to download it and deploy it. - iOS: After relaunching, you can log in on your current version. The updated app will be released as soon as Apple approves it. **Known issue:** SMS is currently not working within the softphone. We are aware of the issue and are working to restore it. SMS is still available from our web app Level365 Web App Desktop downloads are available here: Softphone for Desktop

iOS: The updated version of the Level365 Softphone is now available on the App Store. SMS: A fix has been implemented, and text messaging is working again within the softphone. Known issues: Duplicate threads: We are currently investigating an issue causing multiple message threads to be created for the same conversation. As a workaround, start a new thread and enter the number using all 11 digits (for example, 13175551234). Previous threads: We are currently investigating importing previous message threads in the softphone applications. All message threads are still accessible in the Level365 Web App.

We are continuing to investigate issues with SMS text messaging in the Level365 Softphone and will provide a further update as more information becomes available. Known issues: - Duplicate threads: Multiple message threads are being created for the same conversation. As a workaround, start a new thread and enter the number using all 11 digits (for example, 13175551234). - Previous threads: Previous message threads are not importing into the Level365 Softphone applications for some users. All message threads are still accessible in the Level365 Web App.

This incident has been resolved. Login was restored for all versions of the Level365 Softphone in an earlier update, the number formatting issue for text messages has been fixed, and previous message threads have been restored in the softphone. We are still investigating an issue causing some text messages to create multiple threads, and a version update is pending. Going forward, updates will be posted on our Updates Page. If you experience any further issues, please contact our support team at support.level365.com.

We are currently investigating reports of some users being unable to log in to the Level365 Web App (app.level365.com). Our team is actively working to identify the cause, and further updates will be provided as more information becomes available.

We are continuing to investigate reports of issues with the Web App related to logging in and components not loading properly once logged in. Further updates will be provided as more information becomes available.

We are continuing to investigate reports of some users being unable to log in to the Level365 Web App (app.level365.com). Our team has identified the cause and is working on a fix. We will provide a further update once it has been implemented.

We are continuing to work on a fix for the login issues affecting some users of the Level365 Web App (app.level365.com). We will provide a further update once the fix has been implemented.

A fix has been implemented for intermittent issues affecting some users of the Level365 Web App (app.level365.com). We are continuing to monitor the situation. If you experience any new issues, please contact our support team at support.level365.com.

We have monitored and confirmed that all services are functioning as expected, with no new reports of issues. This incident is now resolved. If you experience any further problems, please contact our support team at support.level365.com.

We are investigating reports of calling issues following the completion of our recent scheduled maintenance. Some users may experience intermittent interruptions when making or receiving calls. Our team is actively working to restore normal calling service as quickly as possible. We will provide another update as more information becomes available.

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

This incident has been resolved. All reported calling issues have been resolved, and no additional issues have been reported. We apologize for any inconvenience this may have caused. If you need further assistance, please contact our Support Team at support.level365.com.

On August 12, Level365 performed standard maintenance on core servers as part of ongoing work to increase infrastructure capacity. During the maintenance, device registrations were temporarily moved to an alternate server to maintain connectivity and minimize service interruptions. Following the maintenance, we identified that a small number of devices were having difficulty registering with the platform. Our investigation found that the alternate server had incomplete device-level information due to a data replication issue. This only affected a small subset of devices but prevented those devices from registering properly and receiving calls. Once identified, our team worked directly with affected users to restore their devices. We also identified the underlying replication issue and deployed a corrective fix to address any remaining registration problems and to prevent this from occurring again in the future.