54 recorded Clearlyip incidents since November 2024, with official updates, affected components, duration and resolution information.
We are receiving reports of outbound call failures with Clearly Cloud USA, but it does not appear to be affecting all users. Engineers are investigating.
This issue has been resolved since 9:45 CDT
We are current investigating an issue where outbound calls to a small percentage of rate centers are failing for customers. Note that this only affects customers directly connecting through our XCast platform.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing an increase in mail delivery delays for messages originating from our platforms towards Microsoft mail services.
Queue processing continues successfully, though slowly as Microsoft accepts mail from our platform(s). We expect to see acceptance rates increase over time as well. Engineering continues to monitor activity and delivery improvements.
We continue to monitor for improved mail delivery rates to Microsoft mail services.
While we are still seeing delays in delivering mail to Microsoft mail services, acceptance rates are continually improving and the current backlog has been almost completely processed. We are continuing to monitor for performance and will close this out once we are satisfied with consistent delivery rates.
Mail continues to flow normally and at expected deliverability rates without delays.
We are current investigating intermittent call quality issues with inbound calls with our upstream carriers
Upstream carrier has resolved the issues at approximately 9:13am CST
Several reports of poor audio quality on inbound calls were received beginning around 6:30 AM CDT. Investigation revealed the issue was region-specific, involving an upstream carrier who was promptly notified. We observed the issue to be fully resolved sometime shortly after 9AM CDT.
We are currently investigating issues with our US East trunking servers that is causing completion issues and audio issues.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with our CA-East trunks and have taken them offline at this time.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
IS NOC is reviewing reports of connectivity issues for some Pulsar360 hosted PBXs in the Toronto region.
Work continues to isolate and find the root cause for connectivity interruptions in the Toronto region.
IS NOC has identified and resolved the issue(s) responsible for connectivity interruption. We are seeing alarms clearing at this time and will continue to monitor.
All services remain stable and operational, free from the previously experienced issues.
We are currently investigating an issue which is affecting chat/sms on Clearly Cloud USA - w
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing some isolated connectivity issues in our US-Central region facilities. They seem to be transient in nature and quick to assert/resolve. We are working with our upstream provider(s) and monitoring closely.
This incident has been resolved.
Our US-Central datacenter is experiencing routing issues at this time. Intermittent problems are resulting from this.
Our upstream connectivity provider(s) are experiencing degraded network performance which is affecting ClearlyIP/14IP services. They are working diligently to resolve this issue.
Work continues by our upstream provider(s) to isolate and resolve the root connectivity issues.
Work continues by our upstream provider(s) to isolate and resolve an apparent DDoS attack affecting multiple customers at the US-Central facilities.
We are seeing recovery but are continuing to monitor the situation while our upstream provider(s) work towards a full resolution.
We are seeing degraded connectivity once again, affecting services in US-Central. We are awaiting updates and progress reports from our upstream provider(s).
We are once again seeing recovery and are continuing to monitor the situation. Our upstream provider(s) have confirmed positive progress towards resolution of this ongoing DDoS event.
Latest updates from our upstream provider(s) indicate a full restoration of all services and connectivity. We are confirming the same and continue to see clean network operation at this time. We will continue to monitor.
Connectivity has remained stable.
**Summary / Impact** On the afternoon of May 31st, 2026, 14IP's network operations group began to observe connectivity issues with resources located at its US-Central \(MKE\) data center. The team began working with their counterparts at the data center facility to understand the nature of the problem. It was quickly determined that a distributed denial of service \(DDoS\) attack targeted upstream was affecting all tenants of the data center. Significant malicious traffic \(exceeding 450gbps\) was measured upstream during the peak of the attack which overwhelmed equipment as well as primary, secondary, and tertiary links. This traffic was mitigated through coordinated, escalating filtering with upstream transit providers, as well as internal engineering to stabilize routing. During the incident, connectivity to systems and services primarily located in this data center were impacted significantly for periods of time between approximately 2 PM ET and 9:30 PM ET. This included Clearly Cloud, ComXchange hosted, Xivea, Business Connect, EPlatform, and several other systems. \(US-East trunking services continued to operate during the US-Central incident.\) **Follow-Up** Several facility-level network and system improvements have been implemented following the incident which should reduce the risk of future occurrences. This includes the deployment of additional DDoS scrubbing capacity, improved granularity for detecting attacks, additional fiber capacity upstream, as well as core network enhancements. 14IP plans additional improvements to its systems and operations to improve platform resilience and flexibility when responding to future incidents.
An upstream Canadian carrier is currently having issues. This may affect incoming calls routed through that carrier, but is limited to ONLY Canadian DIDs through that carrier. Outbound should not be affected. At this time, we have no information from the carrier on ETA.
The upstream carrier is now routing properly. We are monitoring and waiting on more information related to the outage.
This incident has been resolved.
The team is investigating Call Panel on Clearly Cloud USA displaying a bad certificate.
This incident has been resolved.
We are seeing issues with provisioning and registration of some Grandstream devices. The team is actively reviewing the situation
We have implemented a fix. If you are still having issues with your devices, please contact us by emailing [email protected] and we can assist you further.
This incident has been resolved.
The team has identified the issue and is currently working on a fix.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue with Call Panel on Clearly Cloud Canada.
We are continuing to investigate this issue.
A fix is being implemented. If you still are experiencing issues, please open a support ticket and the team will assist.
This incident has been resolved.
The team is currently investigating an issue with Clearly Cloud USA
The team has identified the issue and should be resolved quickly.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating inbound and outbound calling issues with Clearly Cloud US platform.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
SIP2 and Proxy55 are not responding. Calls routing to failover trunks
