62 Cytracom incidents · 2025年8月 — official updates, affected components, duration and resolution details.
コントロールワンの管理ポータルやデバイス管理 API を原因としている問題について調査し、よりゆっくりとリクエストに応じます。 管理ポータルは、レスポンシブで表示できず、接続しようとするControlOne Agentは、接続が困難になる可能性があります.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、一部の顧客のインバウンドコールに影響を及ぼす問題について調査しています。 破壊は、当社の上流サービスプロバイダの1つに影響を及ぼすファイバネットワーク障害に関連しています。 当社のチームは、プロバイダと協力して、回復を監視し、通常のインバウンドコールをできるだけ早く復元します。 アウトバウンドコール(このプロバイダーを介してルーティングされていない)、その他のサービスは現在影響されていません。 情報が増えるにつれて、追加アップデートが提供されます.
今後もこの問題について調査を続けてまいります.
当社は、顧客のサブセットに影響を与える断続的なインバウンドコールドロップのソースを特定しました。 上流ボイスキャリアは、音声トラフィックの部分にパケット損失を引き起こしたネットワークインシデントを確認しました。 これにより、インバウンドコールが断続的に接続後にリングを中断またはドロップすることができません。 当社のキャリアは、通常の呼び出し行動を回復するために積極的に取り組んでおり、影響を受けたアカウント間での呼び出し品質を密接に監視しています。 最新情報をお届けいたします.
当社の上流キャリアは、予想される呼び出し行動を観察し、引き続き安定性を監視します.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、米国南西部(LAX)地域における部分的なサービス劣化を調査しています。 一部の顧客は、通常のレイテンシーと断続的な接続よりも高い経験があります.
修正を実装し、結果を監視しています.
南カリフォルニアの複数の地域キャリアネットワークパスに影響を及ぼすサードパーティ製のファイバーカットが修理され、サービスが復元されました.
公式のインシデント更新を自動翻訳しています。
現在、米国南東部(ATL)地域における部分的なサービス劣化を調査し、お客様のサブセットに対するブリッジ接続に影響しています.
影響を受けたワークロードは、コンピュートホストを変更するために再スケジュールされ、結果を監視しています。 影響を受けたハードウェアは、影響を受けた物理コンポーネントの是正措置を受けます.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、米国南西部(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.
現在、ControlOne サイトのサブセットによる問題の調査を行い、ControlOne ポータルで不適切な 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.
公式のインシデント更新を自動翻訳しています。
現在、米国南東部(ATL)地域における部分的なサービス劣化を調査しています.
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.
インバウンドやアウトバウンドの失敗に影響を及ぼす問題を調査しています。 この問題を引き起こした誤った構成を特定しました。 修正に取り組んでおり、すぐに更新します.
修正が実装され、通常通り呼び出しが流れています。 私たちは、他のあらゆる問題について密接に監視しています.
この事件は解決しました。 追加のステップを実行して、自動設定管理が宣言されたメンテナンスウィンドウの外にトリガーされないようにしました。 弊社では、この事態に遭われたご迷惑をおかけいたしますが、何卒ご了承ください.
公式のインシデント更新を自動翻訳しています。
米国・南中央ControlOne地域における顧客のサブセットに対する部分的なサービス劣化による問題を特定しました。 ControlOne Bridge は、断続的な接続を経験する可能性があります。 ControlOne エージェントは、断続的なコネクティビティや「再試行」ステータスを体験できます
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
米国南東部のControlOne地域の顧客を15%のサブセットに部分的なサービス劣化を引き起こす問題を特定しました。 ControlOne Bridge は、断続的な接続を経験する可能性があります。 ControlOne エージェントは、断続的なコネクティビティや「再試行」ステータスを体験できます
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
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.