62 Cytracom incidents · 2025年8月 — official updates, affected components, duration and resolution details.
我们正在调查一个让控制一号的"管理门户"和设备管理API比通常更慢地响应请求的问题. 管理门户可能似乎没有反应,试图连接的控制一代理人可能会遇到连接困难.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查一个影响一些客户的入境电话的问题。 中断是因为纤维网络的故障影响到我们的上游服务供应商之一。 我们的小组正在积极与供应商合作,以监测恢复情况并尽快恢复正常的入境呼叫。 外线呼叫(除非通过此提供者)和其他服务目前没有受到影响。 一旦获得更多信息,我们将提供更多最新情况.
我们正在继续调查这一问题.
我们查明了间歇性入境电话滴滴的来源,影响到一部分客户。 我们的上游语音载体已经证实 网络事件导致 部分语音流量丢失 这导致接通电话时断时续地无法接通或接通后不久即下降。 我们的航空母舰正在积极努力恢复正常的呼叫行为,我们正在密切监测受影响账户的呼叫质量。 我们将提供更多信息.
我们的上游航母正在观察预期的召唤行为,并将继续监测稳定情况.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们目前正在调查美国-西南(LAX)地区的部分服务退化。 一些客户的延迟度和间歇性连通性高于正常水平.
一项措施已经执行,我们正在监测结果.
影响南加州多条区域航母网络路径的第三方纤维切削被修复,服务被恢复.
自动翻译自官方事件更新。
目前,我们正在调查美国东南部地区发生的部分服务退化,影响到一部分客户的桥梁连接.
受影响的工作量已重新安排到不同的计算主机,我们正在监测结果。 受影响的硬件将对受影响的物理部件采取补救行动.
这一事件已经得到解决.
自动翻译自官方事件更新。
目前,我们正在调查美国-西南(LAX)地区发生的部分服务退化,影响着一部分客户的桥梁连接.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
We have identified an issue affecting ControlOne Agent geolocation services. Agents may intermittently fail a location in the portal, or fail a device posture check that requires a location fix. As a workaround partners can remove geolocation from the policy.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
我们正在调查一个导致控制一号网站子集在控制一号门户网站上报告不正确的ISP状态的问题. 这仅仅是视觉问题,并不影响网站的连接.
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.
自动翻译自官方事件更新。
我们目前正在调查美国东南部地区部分服务退化的情况.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
自动翻译自官方事件更新。
We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to configuration changes more slowly than usual. The management portal may appear unresponsive until this clears.
This incident has been resolved.
我们正在调查一个影响出入境电话故障的问题。 我们发现了造成这一问题的不正确的配置。 我们正在寻找解决办法,并将很快予以更新.
已经执行了一项措施,我们的呼吁也一如既往。 我们正在密切监测任何其他问题.
这一事件已经得到解决。 我们采取了额外的步骤,以便自动化配置管理不会在宣布的维护窗口之外触发. 我们对此造成的破坏表示歉意.
自动翻译自官方事件更新。
我们已查明一个导致美国-中南第一控制区部分客户服务退化的问题。 一号控制桥可能出现间歇连接 控制一号特工可能遭遇间歇连接或"重试"状态
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们找出了一个问题,导致美国东南第一控制区15%的客户部分服务退化。 一号控制桥可能出现间歇连接 控制一号特工可能遭遇间歇连接或"重试"状态
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
One of the servers in our fleet experiencing network connectivity issues and our engineering team is investigating. If you are in that server, you may experience intermittent call failures. We will resolve this quickly and thanks for your patience.
We restarted the network interface and the calls should flow as usual. Thanks for your patience during this issue.
This incident has been resolved.
We are currently investigating an issue causing partial inbound and outbound call failures for some customers. Affected users may experience failed call attempts, delayed call setup, or intermittent call completion issues. The issue does not appear to impact all calls or all customers. Our engineering team is actively investigating and working to restore full calling functionality. We will provide additional updates as more information becomes available.
We have taken corrective action to address the partial inbound and outbound call failures affecting some customers. A small number of call processing servers were restarted to restore normal call flow. Call traffic has recovered, and we are currently monitoring the platform to confirm continued stability. Some users may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident. We will continue monitoring and provide a final update once the issue is fully resolved.
The issue causing partial inbound and outbound call failures has been resolved. Corrective action was taken by restarting a small number of call processing servers, which restored normal call flow. After continued monitoring, inbound and outbound calling have remained stable. Some customers may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident window. We apologize for the disruption and appreciate your patience while our team worked to restore service.
We are currently investigating an issue affecting the Realtime Call Center dashboard. Call center event processing is delayed due to a backlog in the event processing service, which may cause dashboard status, agent state, and call activity updates to appear stale or delayed. Inbound and outbound calling are not impacted. Calls continue to route and complete normally. Our team is working to restore realtime event processing and will provide updates as we make progress.
**Update: Realtime Call Center Dashboard Delays** We have identified the issue affecting the Realtime Call Center dashboard. A backend event processing service became degraded due to a high volume of invalid messages, which caused call center status updates to be delayed. A fix has been implemented, and queued events are now being processed. The dashboard may continue to show delayed or stale status information while the backlog clears. Inbound and outbound calling remain unaffected. Calls continue to route and complete normally. We expect the Realtime Call Center dashboard to be current within the next hour.
Queued events are now processing concurrently, and the Realtime Call Center dashboard is recovering. Due to the backlog and out-of-sequence event processing during recovery, some dashboards may show incorrect call-waiting counts for today. We are working to correct these values where possible. Inbound and outbound calling remain unaffected. Calls continue to route and complete normally. Realtime dashboard activity is expected to normalize as event processing catches up. Daily dashboard statistics should display as usual starting tomorrow.
This issue has been resolved.
We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.
We have identified and corrected the issue. Call Detail Records (CDRs) in Insights during the incident will be available within next 12 hours. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.
All backlog Call Details Records have been processed. This issue is now resolved.
We are currently experiencing a backlog in our call event processing system, which may cause delays in event-related updates. This may impact CDR processing, BLF status updates, and voicemail arrival indicators. Inbound and outbound calling remain operational, and voicemail delivery is not impacted. Our team is actively working to clear the backlog and will continue to monitor the system.
We have identified and corrected the issue that caused a backlog in our event processing pipeline. The issue was related to a failed event consumer, which has now been restarted, and queued messages are processing successfully. Some Call Detail Records (CDRs) in Insights may continue to be delayed for the next few hours while the CDR processor catches up on previously delayed events. New events are processing normally and are not expected to experience delays. Inbound and outbound calling, voicemail delivery, and new CDR processing are not impacted at this time. We will continue monitoring until the backlog is fully cleared.
The backlog processing has been completed. This issue is now resolved.
We are currently investigating an issue causing intermittent inbound and outbound call failures for some customers. Our engineering team is actively working to identify the root cause and restore normal call processing. We will provide an update as soon as more information is available.
We have identified and mitigated the issue that caused intermittent call setup failures for some customers. The issue was related to a degraded backend component that impacted call processing on a subset of voice infrastructure. Our engineering team applied corrective action, and calls are now processing normally. We are continuing to monitor the platform closely to ensure stability.
This incident has been resolved.
We are currently investigating intermittent inbound and outbound call failures affecting some customers. Our team is actively working to identify the issue and will provide updates as they become available.
We identified an issue affecting call processing on a subset of voice servers, which resulted in intermittent inbound and outbound call failures for some customers. Our engineering team applied corrective action, and call processing has returned to normal. We are continuing to monitor the platform closely to ensure stability.
The issue causing intermittent inbound and outbound call failures has been resolved. Our engineering team identified a capacity constraint in a backend call processing service and applied corrective action. Calls are now processing normally, and the platform remains stable.
This incident has been resolved.
We have identified that our third-party CNAM provider is not responding within our required performance thresholds. To prevent call completion delays or failures, we are temporarily bypassing Caller ID name resolution for affected calls. During this time, calls may complete without a resolved caller identity or display name. Call delivery itself remains operational. Our team is working on a remediation plan and expects to implement a permanent solution within the next 72 hours. We will continue to monitor the service and provide updates as progress is made.
The Caller Id resolution is working as expected. We are monitoring for any further issues.
The CNAM (Caller ID) service is fully functional without any performance constraints.