Is Clearly IP 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 will be undergoing scheduled maintenance during this time.

One of Clearly IP's upstream network providers will be performing a significant maintenance event at the CA East Datacenter. While all precautions have been taken to ensure this is a non-service affecting event, the vendor's scope of the work does present some persistent risk of intermittent connectivity during the maintenance period. We expect any interruptions to be brief.

During the early afternoon of Friday May 16, our engineering team detected a potential issue and proactively moved production SIP services onto a secondary redundancy system in an abundance of caution in order to prevent a widespread service disruption. For approximately an hour, the secondary system operated with limited BLF functionality but processed calls and registrations normally. There may have been very brief issues with call setup or registration during the failover and failback process. BLF features were restored to normal functionality at the conclusion of the failback operation.

This incident has been resolved.

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

Calls and registrations are working as expected, however BLF lights, including parking and extension status, are not functioning at this time.

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

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

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

The team is actively working on an issue where some users are losing registration with Clearly Cloud US.

During the morning of Wednesday May 14, we began receiving reports of intermittent issues from Clearly Cloud users in parts of the US with registrations and call completion. The engineering team immediately began investigating and closely monitored the performance of all related systems for the next several hours, identifying the cause of the problem. A full analysis confirmed that call signaling messages were being jammed up during three timeframes, each approximately ~13 minutes, ~6 minutes, and ~5 minutes in duration. The cause of the problem was a replica \(spare\) database server unable to keep up with the synchronization from the primary systems, causing widespread delays and backups completing tasks like registration handling. Once the cause was identified as a non-production server, our team began to take immediate action by disabling its role and disconnecting it from the production systems while evaluating what was behind its performance problem. This prevented additional issues beyond those experienced. Metrics and logs indicated a likely hardware issue. Thankfully, ClearlyIP's recent investments in improving its Central US datacenter operations meant our team could quickly move the replica database to this newer environment. That migration was completed several hours after the issues began, situating the replica server in the new environment. It was then restored to service late afternoon. No similar Clearly Cloud issues were observed after the replica server was taken out of service, or since it was restored to service. Our teams will continue to proactively monitor the performance of these systems and study additional improvements which can minimize the impact of similar circumstances for the future.

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.

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

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

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

We are seeing intermittent registration issues on our Clearly Cloud US servers.

Over the course of approximately two hours, several customers in specific regions reported intermittent Call Panel connection status messages and registration timeouts with some phones.  Our support team investigated the reports and enlisted assistance from engineering while attempting to reproduce.  The problem was not definitively identified while issues were reported and may be attributable to connectivity issues or other factors outside ClearlyIP's network, but our teams will continue monitoring the situation while awaiting additional reports.

This incident has been resolved.

We are continuing to monitor for any further issues.

After receiving several customer reports of issues relating to registration and call processing, we have been unable to replicate or confirm any problems. There have been no more reports of issues for the past 20 minutes. Our teams will continue to monitor.

Multiple users have reported issues with no audio on calls, unable to dial out and other call oddities.

We are currently investigating reports of odd call issues from a subset of users.

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 are currently investigating this issue with calling with our CA-East region.

An issue occurred on April 29th during a failover operation between elements of Clearly Cloud's core infrastructure.  This impacted Canada customers' ability to register phones and place calls for approximately 4 minutes.   Most elements of Clearly Cloud's infrastructure are designed with several redundancies and  failover occurring seamlessly without impact to customer operations.  In this case, the initial failover operation completed as expected, but the backup components did not handle the traffic they received as intended. Both the cause of the failover and the issue which caused the backup components to properly handle traffic have been identified. Improvements have been planned which should prevent similar failures.

This incident has been resolved.

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

We are currently investigating this issue.

For approximately 14 minutes during the morning of April 28th, some US customers experienced intermittent issues with phone registration and call setup.  The issue resulted from a high level of database load and was resolved rapidly by the engineering team.  The causes of the database traffic in question have been identified and measures are being implemented which should prevent recurrence under similar scenarios.

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 are currently investigating this issue.

Impacts to connectivity at the upstream vendor have been resolved.

Clearly IP NOC personnel have identified an issue impacting connectivity to US East SIP Trunking services by an upstream vendor. All other SIP Trunking locations/regions remain unaffected.

Our response began immediately when availability monitors detected the possibility of an issue with Clearly Cloud operations.  It was confirmed that some Clearly Cloud operations were impacted and the NOC team worked to restore full functionality as quickly as possible.  As service was restored, teams began to identify the sequence of events which caused the description and root causes.   ‌ Ultimately, it was determined that a core network switch malfunctioned for a very brief period, automatically triggering protective high-availability systems.  This led to a number of resources shifting to work around the perceived issue, leading to manual intervention due to the nature of the actual equipment failure.  ClearlyIP has initiated a proactive replacement of all switches of the same type, revised incident response protocols, and improved processes which will both reduce the likelihood of recurrence and significantly reduce recovery times for other situations.

This incident has been resolved.

All system checks have been completed and issues are resolved.

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

Clearly Cloud is now resolved.

The team is still working through checks.

The team has identified the issue and is working on resolution.

Call Panel and Management interface offline on Clearly Cloud USA

This incident has been resolved.

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

We are currently investigating an issue with ComXchange licensing servers which may result in an invalid license status.

At approximately 05:39 CST, our web service began restarting irregularly. This did not affect inbound or outbound calling or registration, but did result in the Management and Call Panel web properties to fail to load. At 07:59 CST, the service was taken completely offline, and restarted cleanly, and service resumed.

Web access has been fully restored.

We are currently investigating an issue with Clearly Cloud USA Admin GUI and Call Panel.

The issue was resolved at approximately 16:00 CST.  Details about the cause of the issue and its scope have been emailed to all customers and partners.  If you have not received this message, please email your account representative or contact support.

The issue was resolved at approximately 16:00 CST. Details about the cause of the issue and its scope have been emailed to all customers and partners. If you have not received this message, please email your account representative or contact support.

We are continuing to monitor for any further issues.

The team has stabilized the system. If you are still experiencing issues, please open a ticket at support.clearlyip.com. Our team is monitoring and verifying full system recovery.

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

We are still seeing intermittent issues with incoming and outgoing calls, primarily with our Clearly Cloud US platform. The team is still working on this.

Data center connectivity is restoring, and systems should be coming back online now. If you are still experiencing issues, please open a ticket at support.clearlyip.com. Our team is monitoring and verifying full system recovery.

Clearly Cloud USA is still reporting some issues.

Update: Data center connectivity is restoring, and systems should be coming back online now. If you are still experiencing issues, please open a ticket at support.clearlyip.com. Our team is monitoring and verifying full system recovery.

We are seeing alerts closing and believe the issue may be resolved. The team is actively checking all systems to verify.

We are currently investigating a data center internet issue that is leading to high delays on inbound and outbound calling.

This was a partial outage which affected customers utilizing our Clearly Cloud USA Cloud PBX product. Customers may have intermittent registration and call issues on our Clearly Cloud USA Cloud PBX product related to an extreme CPU load change. The root cause of this was due to internal API calls that were abnormally high. As a result of this issue, the engineering team has adjusted the rate limits on the affected APIs to better deal with the situation that occurred. This helped bring our load down and back to normal levels, resolving the issues.

This incident has been resolved.

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

We are investigating a possible network issue.

This incident has been resolved.

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

We are currently investigating this issue.

One of the queue nodes began behaving erratically, so it was taken offline and a different node brought up to replace it.

This incident has been resolved.

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

Some users are experiencing issues with queue calls not making it to agents. The team is investigating.

Related to Feb 9, 2025 issue, the storage server was decommissioned, which required maintenance to Clearly Cloud USA to complete.

This incident has been resolved.

We will be undergoing maintenance on a backend storage server that may cause intermittent calling issues with our Clearly Cloud USA servers.

A back end storage server is experiencing issues. Our monitoring detected the issues and our team forced failovers to mitigate the storage server issue.

This incident has been resolved.

The team has identified the issue and is taking steps to correct.

Our monitoring systems detected an inconsistency in our database servers, causing our central trunking servers to fail to take calls. NOC put the central servers into maintenance mode, causing all calls to be routed though different trunking servers \(depending on individual customer setups\) and began resolving the database issue. Once resolved, the central trunking servers were brought back online.

This incident has been resolved.

We have identified an issue with our US Central servers and our team is investigating. If you are setup with multiple trunking servers, there should be no issue. If you are using only our central servers, you will want to change your registration to other servers or the time being.

Cloud Flare DNS was having issues with Chicago location \(See [https://www.cloudflarestatus.com/](https://www.cloudflarestatus.com/) for more info on their issue.\) For customers using Cloud Flare as their DNS \(1.1.1.1 or 2.2.2.2\), updating your DNS appears to resolve the issue. We use Cloud Flare DNS as well as other DNS providers, and as a precautionary measure, we removed Cloud Flare DNS from critical areas to limit the delays that may be caused by Cloud Flare.

This incident has been resolved.

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

We are currently investigating, however this appears to be related to Cloud Flare issue. See https://www.cloudflarestatus.com/ for more info on their issue. For customers using Cloud Flare as their DNS (1.1.1.1 or 2.2.2.2), updating your DNS appears to resolve the issue. We use Cloud Flare DNS as well as other DNS providers, and as a precautionary measure, we are removing Cloud Flare DNS from critical areas to limit the delays that may be caused by Cloud Flare.

We are currently investigating an issue causing call disruption, registration issues, and website access.

We are currently investigating this issue.

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.

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

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.

The team is currently investigating an issue affect Clearly Cloud Canada which may affect registrations and calls on the platform

This incident has been resolved.

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

The problem has been found and a fix is being implemented shortly.

We are currently investigating an issue where some user or entire realms are not able to dial out. Inbound does not appear to be affected.

This incident has been resolved.

The team is already resolving the issue.

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 are currently investigating registration and calling issues with Clearly Cloud USA

This incident has been resolved.

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

The team is actively correcting the issue.

This incident has been resolved.

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

The problem has been found and a fix is being implemented.

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

We are currently investigating this issue.

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 are aware of issues with SMS and chat messages on Clearly Cloud Canada. The team is actively investigating the issue and will update when we have more information to share.

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

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

A fix has been implemented and system integrity checks are proceeding.

We are currently investigating an outage in our Montreal datacenter that is affecting multiple systems.

Queues alerted with issues and some users may have experienced dead air when calling in. Monitoring alerted and the team resolved.

We are currently investigating an issue with Queues on our Clearly Cloud US instance.

This incident has been resolved.

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

We are still investigating, however most calls are working. There may be potential for more call issues, so we are leaving the status as identified.

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

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

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

We are currently investigating this issue.

This incident has been resolved.

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

Clearly Cloud Canada is experiencing issue with calling and registration. The team is investigating now.

Our systems handled this as expected. Memory errors were detected, and to avoid potential issues, our systems moved instances as expected. Our NOC team did do integrity checks on the affected systems and downtime was minimized.

Our systems detected a memory issue on one of our high availability nodes, and our systems began shifting instances to other nodes. This resulted in high load and short outages while systems were moved and integrity checked.

All systems are operational.

We are reviewing all hosted systems to verify integrity.

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

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 are currently investigating an intermittent issue with calls not succeeding and Call Panel not able to make calls.

After monitoring for a couple days the team has considered this resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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

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

The team is currently investigating why the trunking portal, cloud devices portal, and SMS API are unavailable. In addition, we are seeing degraded performance with our SendFax.to service. The team is working on identifying the issue and will provide more information when it’s available.

The issue was related to a backing storage server and the team corrected the issue immediately after receiving the alerts.

Issue has been resolved. The team is monitoring

Some users are experiencing calling issues inbound and outbound.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently aware of an issue with an upstream taxation provider which may cause issues with purchases in the trunking store. We are working closely with the vendor on a resolution and will update when we have additional information to share.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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

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

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are currently monitoring that calls are functioning properly.

We are continuing to investigate this issue.

We are currently investigating this issue with intermittent calling issues on Clearly Cloud US

This incident has been resolved.

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

The team is actively working on a fix. All calls are being routed through different servers.

This incident has been resolved.

CDM is currently undergoing emergency maintenance and is in read only mode at this time.

This incident has been resolved.

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

We are currently investigating this issue.

A patch has been implemented to avoid this issue in the future.

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

We are currently investigating this issue.

This incident has been resolved.

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

We are currently investigating intermittent issues with inbound/outbound calling on Clearly Cloud USA

This incident has been resolved.

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

The team is actively investigating issues with intermittent call delays on outbound and inbound.

This incident has been resolved.

We are currently monitoring the situation.

We are continuing to investigate this issue.

We are currently investigating issues with inbound and outbound calls taking a long time to connect, or not connecting at all from some areas.

This incident has been resolved.

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

We are currently investigating an issue with registration on our Clearly Cloud US systems.

This incident has been resolved.

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

We are currently investigating this issue.

This incident has been resolved.

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

The issue has been identified as an issue with one of our upstream providers. We are actively engaged with the provider and working with them on a resolution.

We are investigating of an issue with checkout not working in the trunking portal.

This incident has been resolved.

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

We are currently investigating an issue with phones not being able to register to Clearly Cloud US, this includes Call Panel Softphones