Looking for an update now? Check the current status, or follow Cytracom for future changes.
86.7%of 30 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
84%
25
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
ControlOne service degradation in the US-Midwest (ORD) Region
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to requests more slowly than usual. The management portal may appear unresponsive, and ControlOne Agents attempting to connect may experience difficulties connecting.
Our upstream carrier is observing expected calling behavior and will continue to monitor for stability.
identified
We have identified the source of intermittent inbound call drops affecting a subset of customers. Our upstream voice carrier has confirmed a network incident causing packet loss on a portion of voice traffic. This is resulting in inbound calls intermittently failing to ring through or dropping shortly after connection.
Our carrier is actively working to restore normal calling behavior, and we are closely monitoring call quality across affected accounts. We will provide updates as we have mor...
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating an issue affecting inbound calls for some customers.
The disruption is related to a fiber network failure impacting one of our upstream service providers. Our team is actively working with the provider to monitor recovery and restore normal inbound calling as quickly as possible.
Outbound calling (unless routed through this provider) and other services are not currently impacted.
We will provide additional updates as more information becomes available.
ControlOne partial service degradation in the US-SouthWest (LAX) Region
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating a partial service degradation in the US-SouthWest (LAX) Region. Some customers are experiencing higher than normal latency and intermittent connectivity.
August 2026
ControlOne partial service degradation in US-SouthEast (ATL) region
Impacted workloads have been rescheduled to alternate compute hosts and we are monitoring the results. The impacted hardware will undergo remediation actions for the affected physical components.
investigating
We are currently investigating a partial service degradation in the US-Southeast (ATL) Region impacting bridge connectivity for a subset of customers.
Legacy Incident Archive
25 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
UCaaS: Realtime Queue Status Dashboard Not Updating
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 sta...
identified
**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...
investigating
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.
UCaaS: BLF status and Call Detail Records Delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
identified
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.
UCaaS: Call Details Records and Presence
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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, ...
identified
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.
UCaaS: Outbound Call Failure
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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.
UCaaS: Inbound/Outbound Call Failures
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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.
May 2026
UCaaS: Caller ID Name Resolution
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The Caller Id resolution is working as expected. We are monitoring for any further issues.
identified
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 cont...
UCaaS: Intermittent Inbound Call Failures
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have identified and mitigated an issue that was causing intermittent call completion failures.
The issue was related to a third-party CNAM lookup service responding slower than expected. This delay caused some calls to fail over to our secondary data center, which resulted in intermittent disruption to call completion.
We have temporarily disabled this dependency, and calls are now completing as expected. We are continuing to monitor call completion and overall service stability.
identified
The UCaaS platform is experiencing intermittent inbound/outbound call failures. We are investigating the root cause.
We identified an issue with a third-party call-signing service provider and temporarily disabled that dependency to restore normal call flow. Calls are currently completing as expected. We are continuing to monitor call completion and will implement a remediation plan to reduce future impact from this dependency.
identified
The issue has been identified and a fix is being implemented.
monitoring
In our primary data center inbound/outbound calls are failing in several voice Pods and they are being routed to our secondary data center. Callers may experience intermittent call failures until we resolve this issue.
ControlOne partial service degradation in the US-SouthEast (ATL) Region
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating an issue impacting Agent connectivity in our US-SouthEast (ATL) Region.
April 2026
ControlOne API + Management portal increased load times.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to requests more slowly than usual. The management portal may appear unresponsive, and ControlOne Agents attempting to connect may experience difficulties connecting.
