Cytracom Outage History
Uptime record, past incidents, and downtime history for Cytracom.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 70.4% | 27 | 8 |
| May 2026 | 77.4% | 31 | 7 |
| April 2026 | 66.7% | 30 | 10 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
UCaaS: BLF status and Call Detail Records Delayed
Started: Jun 10, 6:43 PM
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.
Jun 10, 8:50 PM
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.
Jun 10, 6:43 PM
UCaaS: Call Details Records and Presence
Started: Jun 9, 8:32 PM
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, ...
Jun 9, 9:44 PM
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.
Jun 9, 8:32 PM
UCaaS: Outbound Call Failure
Started: Jun 3, 3:10 PM
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.
Jun 3, 3:49 PM
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.
Jun 3, 3:10 PM
UCaaS: Inbound/Outbound Call Failures
Started: Jun 2, 4:11 PM
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.
Jun 2, 4:49 PM
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.
Jun 2, 4:11 PM
May 2026
UCaaS: Caller ID Name Resolution
Started: May 29, 6:41 PM
monitoring
The Caller Id resolution is working as expected. We are monitoring for any further issues.
May 29, 9:02 PM
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...
May 29, 6:41 PM
UCaaS: Intermittent Inbound Call Failures
Started: May 28, 3:20 PM
monitoring
We are continuing to monitor for any further issues.
May 28, 4:58 PM
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.
May 28, 4:47 PM
identified
The UCaaS platform is experiencing intermittent inbound/outbound call failures. We are investigating the root cause.
May 28, 3:20 PM
UCaaS: Intermittent Inbound/Outbound Call Failures
Started: May 27, 7:39 PM
monitoring
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.
May 27, 8:48 PM
identified
The issue has been identified and a fix is being implemented.
May 27, 8:05 PM
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.
May 27, 7:39 PM
ControlOne partial service degradation in the US-SouthEast (ATL) Region
Started: May 21, 2:07 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 21, 3:18 PM
identified
The issue has been identified and a fix is being implemented.
May 21, 3:08 PM
investigating
We are currently investigating an issue impacting Agent connectivity in our US-SouthEast (ATL) Region.
May 21, 2:07 PM
April 2026
ControlOne API + Management portal increased load times.
Started: Apr 23, 12:36 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 23, 2:00 PM
identified
We are continuing to work on a fix for this issue.
Apr 23, 12:54 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 12:47 PM
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.
Apr 23, 12:36 PM
UCaaS Voice Services Impairment
Started: Apr 17, 10:51 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 18, 12:16 AM
investigating
Cytracom Engineering has identified an issue impairing outbound calls for a subset of our customers. We are investigating the root cause and working towards a full resolution. As updates become available, they will be posted here.
Apr 17, 10:51 PM
UCaaS: Desktop App
Started: Apr 7, 4:22 PM
monitoring
We are continuing to monitor for any further issues.
Apr 7, 4:22 PM
monitoring
Some customers reported issues with inbound and outbound calls on the Desktop App. Affected users were advised to log out and log back in to resolve the issue.
Apr 7, 4:22 PM
UCaaS: Call Parking Issue for small subset of D2 devices
Started: Apr 6, 3:27 PM
monitoring
A limited number of D2 devices (~12 endpoints) experienced an issue with call parking due to a firmware defect. This is not a service outage and does not affect the broader UCaaS platform or other device types.
The issue has been identified, and a remediation plan is in progress. Affected devices will be updated to resolve the issue. We are continuing to monitor and will provide updates as remediation is completed.
Apr 6, 4:55 PM
identified
A subset of customers reported issues with call parking not functioning correctly. The root cause has been identified, and a remediation is being developed.
Apr 6, 3:27 PM
UCaaS: Management Portal Outage
Started: Apr 2, 6:19 PM
monitoring
The service has been restarted. All management functions are operational, and the system is stable.
Apr 2, 7:39 PM
investigating
We are investigating an issue impacting the UCaaS Management Portal.
Apr 2, 6:19 PM
UCaaS: Management Portal Unavailable
Started: Apr 2, 5:23 PM
monitoring
The issue affecting the UCaaS Management Portal has been resolved. Users can now access the portal and perform administrative functions normally.
The incident was caused by a spike in usage that exhausted available HTTP connections to the backend. The affected service was restarted to restore functionality. A plan is in place to increase service capacity to prevent recurrence.
We are continuing to monitor the stability of the service.
Apr 2, 5:53 PM
investigating
The UCaaS Management Portal is currently unavailable, preventing users from accessing administrative functions and configuration interfaces. Core calling services are not impacted at this time; however, administrators are unable to manage users, devices, or settings through the portal.
Engineering teams have been engaged and are actively investigating the root cause. Updates will be provided as more information becomes available.
Apr 2, 5:23 PM