Cytracom Outage History

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.

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.

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.

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.

The Caller Id resolution is working as expected. We are monitoring for any further issues.

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.

We are continuing to monitor for any further issues.

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.

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.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

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.

We are continuing to monitor for any further issues.

A limited number of D2 devices 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.

The service has been restarted. All management functions are operational, and the system is stable.

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.

The upstream routing issue has been resolved. We are observing normal call completion rates across affected routes.

A partial outbound calling issue has been resolved. During the incident, one of our outbound proxy servers stopped processing calls. The affected system was restarted and migrated to a different host, restoring normal service. We are continuing to monitor the platform to ensure stability and are reviewing the event to prevent recurrence.

We are continuing to monitor for any further issues.

A fix has been implemented for the call routing node failure. Inbound and outbound call completion are now functioning correctly.

From our monitoring and telemetry data the issue appears to be resolved and call completion rates are in the normal range.

We are continuing to monitor for any further issues.

We identified an issue with our connecting carrier affecting inbound calls. The carrier has deployed a fix, and inbound calls are now functioning normally.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to address the root cause of the issue. Users may encounter issues adjusting permissions within the Unity portal.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.