外出到一个小比例中心的呼吁失败
- investigating
我们目前正在调查一个问题,即向一小部分收费中心的外出电话对客户来说是失败的。 请注意,这只影响到客户通过我们的XCast平台直接连接.
- identified
这一问题已经确定,一个解决办法正在实施之中.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
53 Clearlyip incidents · 2024年11月 — official updates, affected components, duration and resolution details.
我们目前正在调查一个问题,即向一小部分收费中心的外出电话对客户来说是失败的。 请注意,这只影响到客户通过我们的XCast平台直接连接.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们看到,从我们的平台向微软邮件服务发送的信息的邮件延迟增加.
队列处理继续成功进行,尽管随着微软接受来自我们平台的邮件而缓慢. 我们期望随着时间的推移,接受率也会提高。 工程部门继续监测活动和交付改进情况.
我们继续监测微软邮件服务邮件发送率的提高.
虽然我们仍然看到在向微软邮件服务发送邮件方面出现延误,但接受率不断提高,目前的积压已几乎完全处理完毕。 我们正在继续监测执行情况,一旦我们对一贯的交付率感到满意,我们将结束这项工作.
邮件继续按预期可交付率正常流动,没有延误.
自动翻译自官方事件更新。
我们正在调查断断续续的通话质量问题,与我们的上游航空公司接通了电话
上游航母在大约上午9: 13时解决了这些问题
自动翻译自官方事件更新。
我们正用我们的东方中继服务器 来调查问题 造成完成问题和音频问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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
We are currently investigating this issue.
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.
At approximately 11:27AM ET on November 3, ClearlyIP's NOC team began to receive system alerts indicating excess session activity within its US-East trunking systems. The team's investigation identified unauthenticated INVITE messages being received from unknown IPs as the source of the excess traffic, as well as a customer generating unexpected levels of outbound calls. Steps were taken to mitigate the traffic's impact, including restarting affected services to clear sessions and restore normal status. By approximately 11:55AM ET, the US-East situation was stabilized and session traffic had returned to normal levels. The team has identified a number of improvements and traffic management strategies to help avoid similar incidents which will be implemented in future maintenance events.