Level365 had 15 outages in the last 2 years totaling 147h 54m of downtime — averaging 0.6 incidents per month.
There were 15 Level365 outages since May 21, 2024 totaling 147h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.
This morning, a carrier level issue was identified that affected some outbound calls. Traffic was quickly rerouted and service was restored within approximately 10 minutes. We have continued to monitor and everything has remained stable.
We aqre currently investigating degraded performance on our fax platform
We are continuing to investigate this issue.
We are currently investigating reports of issues impacting some fax services. Our team is actively reviewing the situation to identify the cause and restore full functionality as quickly as possible. Thank you for your patience as we work to resolve this.
We are continuing to troubleshoot the issue impacting some fax services. Our team is actively working toward resolving this as quickly as possible. Thank you for your patience as we work to resolve this.
Issue has been identified and a fix has been deployed. We are monitoring services to ensure the issue is resolved.
We are continuing to monitor to ensure the issue is resolved. Please note that some faxes may be delayed or require additional attempts as the system processes the queued messages. Thank you for your patience as we work to resolve this.
This incident has been resolved. All services are confirmed to be working normally, and the backlog of fax messages has been cleared. We will continue to monitor to ensure continued stability. Thank you for your patience as we worked to resolve this issue.
Cloudflare is currently experiencing a global service outage, which may cause intermittent or unexpected behavior with certain external services. This is a widespread incident affecting a number of services, including (for example) Microsoft 365 and other major platforms that rely on Cloudflare’s network. Level365's core services are not impacted, but some clients may experience side effects related to the broader Cloudflare disruption. If you experience any issues, please contact our support team at support.level365.com. Cloudflare has identified the problem and is implementing a fix. We are actively monitoring the situation and expect service to be restored shortly. You may also follow Cloudflare’s incident updates here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Cloudflare has reported that the earlier global service outage has been fully resolved. Any intermittent issues affecting external services relying on Cloudflare should now be returning to normal operation. Level365 core services were not impacted by this incident. If you notice anything unexpected or need assistance, please reach out to our support team at support.level365.com. For additional details, you may follow Cloudflare’s incident report here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
We are currently investigating issues with device registrations affecting some devices following the recent platform maintenance. Our team is actively working to identify the cause, and further updates will be provided as more information becomes available.
A fix has been implemented and affected devices have successfully re-registered. We will continue to monitor device performance and stability.
This incident has been resolved. The impacted devices have remained online since the fix was implemented, and no further issues have been observed. We apologize for any inconvenience this may have caused. If you need any additional assistance, please contact our Support Team at support.level365.com.
Following the recent scheduled maintenance, some devices did not immediately re-register due to re-syncing with our connections to upstream ISP providers, resulting in temporary service interruptions for affected users. Once the paths were fully re-synced, connections were reestablished and the devices came back online. Our team has reviewed the incident and is making adjustments to reduce the likelihood of similar registration delays in the future. We apologize for the inconvenience and appreciate your patience.
One of our data center providers experienced a catastrophic failure during scheduled maintenance. This failure has taken our East Data Center offline. Due to our platform's design, this should not result in any direct client impact. If you experience any issues or have questions, please contact [email protected].
Our vendor has resolved their issue and we are continuing to monitor the situation.
This incident has been resolved.
We have received notification from an underlying carrier used for text messaging that messages to AT&T destinations may fail to complete. We are working with the affected carrier to restore functionality.
Our carrier has mitigated the issue and are observing expected SMS and MMS behavior. We will continue to monitor for traffic stability.
We have been monitoring outgoing messaging traffic and all traffic is flowing as expected. This issue is resolved. If you are still experiencing issues with messaging, please contact Level365 support.
We are investigating issues with Inbound Caller Name Displaying and will provide updates here soon.
A fix has been implemented and we are monitoring the results.
Inbound CallerID Name is now working properly. If you are still experiencing issues with this, please contact support.
We are investigating issues with with our DC datacenter connectivity. It appears to be a facility issue. We are continuing to investigate and will provide updates here soon.
The issue has been identified as a outage in the DC datacenter area.
Data Center provider has resolved the core issue. We are awaiting more details at this time, however service is considered restored
We are investigating a service disruption with our CallerID Name (CNAME) provider.
Our CallerID Name (CNAME) provider has implemented a fix. We will continue monitoring, please contact Level365 Support if you encounter CallerID Name issues.
This incident has been resolved.
We are currently investigating reports of some faxes not completing.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. No further issues have been reported since services were restored. We sincerely apologize for this interruption and if you have any additional troubles, please contact our support team at support.level365.com.
We are currently investigating reports of some faxes not completing.
We have identified the root cause and are working on getting a fix in place.
A fix has been implemented and we are monitoring the results. Please note that some faxes may be delayed or require additional attempts as the system processes the queued messages.
This incident has been resolved. No further issues have been reported since services were restored. We sincerely apologize for this interruption and if you have any additional troubles, please contact our support team at support.level365.com.
We are currently investigating reports of some phone numbers not displaying in the Level365 Web App as well as reports of desk phones not updating and/or populating the directory. At this time we do not recommend factory resetting devices or making hardware changes.
We have identified the sources causing the reported issues and are working towards getting fixes in place.
We are continuing to work on getting impacted services fixed.
Desk phone updates and directory lookup issues have been fixed. We are continuing to work on the issues related to DIDs not populating in the Phone Numbers Inventory through the Level365 Web App.
All phone numbers should now be visible through the Level365 Web App. We will continue to monitor this issue.
We have not received any reports of additional issues and consider this resolved.
We are currently investigating reports of phone showing "No Service".
We have identified the issue with phone registrations and have restored services. We will continue to monitor for any further issues.
This incident has been resolved. No further instances have been reported since services were restored. Please contact our support team at support.level365.com if you need any further assistance.
An equipment failure occurred on Saturday 6/1/24 at approximately 12:30 pm EST. Personnel were dispatched to the data center to apply a fix. All primary services remained available with some services moving to secondary servers as needed. However, some IP telephones did not re-register to secondary servers causing those devices to be offline. The hardware issue was rectified at approximately 2:00 pm EST. The IP telephones which had been offline then re-registered and came online. No further issues were seen or reported. We apologize for any inconvenience this issue may have caused. We are investigating the specific instances where some devices did not register to secondary servers and we will make the proper adjustments to help reduce future issues.
We are currently investigating reports of call recordings not showing up in Call History.
We have identified the cause of the issue and are working towards a resolution as quickly as we can.
We have implemented a fix and call recordings are starting to populate in Call History. There may be some call recordings from this morning that do not populate and we are working to get those restored.
There have not been any new issues reported regarding call recordings since recording services were restored this afternoon. We consider this incident to be resolved. We are aware there are some recordings from this morning that are not showing up in Call History and we will continue to work towards restoring those call recordings.
_Complications occurred during the 5/21/24 maintenance update, which prevented the recording server from returning online. Personnel were dispatched to the data center to apply a fix. During this time the secondary recording server was still recording calls, they were just inaccessible via our Web App._ _At approximately noon ET, our primary recording server connection was restored and recordings that occurred before our maintenance as well as new recordings were once again accessible. However, call recordings during the downtime were still inaccessible from our secondary recording server. The configuration of the secondary recording server was then updated, which restored all recordings, and will help prevent this type of incident in the future._