Cytracom

All Systems Operational

Voice Services Operational
Call Completion Operational
BLF Presence Operational
Voicemail Operational
Call Center Operational
Caller ID Resolution Operational
SpamGuard Service Operational
Fax Services Operational
Fax Completion Operational
Desktop Fax Operational
Business Messaging Operational
Client Applications Operational
Desktop Operational
Cytracom iOS Operational
Cytracom Android Operational
Contacts Operational
Management Operational
UC Management Portal Operational
Partner Portal Operational
Billing Services Operational
Integrations Operational
ControlOne Operational
ControlOne Management Portal Operational
ControlOne Routing Services Operational
US-NorthEast (EWR) Region Operational
US-SouthEast (ATL) Region Operational
US-MidWest (ORD) Region Operational
US-SouthCentral (DFW) Region Operational
US-NorthWest (SEA) Region Operational
US-SouthWest (LAX) Region Operational
Unity Operational
90 days ago
100.0 % uptime
Today
Unity Portal Operational
90 days ago
100.0 % uptime
Today
Unity Authentication Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jun 7, 2026

No incidents reported today.

Jun 6, 2026
Completed - The scheduled maintenance has been completed.
Jun 6, 22:20 CDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 6, 22:00 CDT
Scheduled - We will be performing a rolling upgrade of several voice servers during this maintenance window. During this time, a subset of customers may experience brief interruptions to inbound and outbound calls while the servers are rebooted.
Jun 3, 11:43 CDT
Jun 5, 2026

No incidents reported.

Jun 4, 2026

No incidents reported.

Jun 3, 2026
Resolved - This incident has been resolved.
Jun 3, 23:06 CDT
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, 10:49 CDT
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, 10:10 CDT
Jun 2, 2026
Resolved - This incident has been resolved.
Jun 2, 15:57 CDT
Update - 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.
Jun 2, 15:56 CDT
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, 11:49 CDT
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, 11:11 CDT
Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026
Resolved - The CNAM (Caller ID) service is fully functional without any performance constraints.
May 29, 18:27 CDT
Monitoring - The Caller Id resolution is working as expected. We are monitoring for any further issues.
May 29, 16:02 CDT
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 continue to monitor the service and provide updates as progress is made.

May 29, 13:41 CDT
Resolved - This incident is marked as resolved. No further inbound call failures were observed.
May 29, 03:19 CDT
Update - We are continuing to monitor for any further issues.
May 28, 11:58 CDT
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, 11:47 CDT
Identified - The UCaaS platform is experiencing intermittent inbound/outbound call failures. We are investigating the root cause.
May 28, 10:20 CDT
May 28, 2026
May 27, 2026
Resolved - Call flow has returned to normal, and calls are completing as expected. We are closing this incident. Our team will continue with the planned remediation work to reduce future impact from this third-party call-signing dependency.
May 27, 17:03 CDT
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, 15:48 CDT
Identified - The issue has been identified and a fix is being implemented.
May 27, 15:05 CDT
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, 14:39 CDT
May 26, 2026
Resolved - Between 7:30–7:45 AM CST, one of our voice servers experienced an issue that prevented it from processing inbound and outbound calls for a small subset of customers. The issue was isolated to a service module on the affected server. We restarted the server, and call processing resumed normally afterward.
May 26, 07:30 CDT
May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.