Cytracom Outage History

Cytracom is up right now

There were 13 Cytracom outages since February 5, 2026 totaling 36h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cytracom.com

Minor April 23, 2026

ControlOne API + Management portal increased load times.

Detected by Pingoru
Apr 23, 2026, 12:36 PM UTC
Resolved
Apr 23, 2026, 03:44 PM UTC
Duration
3h 8m
Affected: ControlOne Management Portal
Timeline · 5 updates
  1. investigating Apr 23, 2026, 12:36 PM UTC

    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.

  2. identified Apr 23, 2026, 12:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Apr 23, 2026, 12:54 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Apr 23, 2026, 02:00 PM UTC

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

  5. resolved Apr 23, 2026, 03:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 17, 2026

UCaaS Voice Services Impairment

Detected by Pingoru
Apr 17, 2026, 10:51 PM UTC
Resolved
Apr 18, 2026, 02:45 AM UTC
Duration
3h 53m
Affected: Call Completion
Timeline · 3 updates
  1. investigating Apr 17, 2026, 10:51 PM UTC

    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.

  2. monitoring Apr 18, 2026, 12:16 AM UTC

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

  3. resolved Apr 18, 2026, 02:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 7, 2026

UCaaS: Desktop App

Detected by Pingoru
Apr 07, 2026, 04:22 PM UTC
Resolved
Apr 07, 2026, 09:13 PM UTC
Duration
4h 51m
Affected: Call CompletionDesktop
Timeline · 3 updates
  1. monitoring Apr 07, 2026, 04:22 PM UTC

    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.

  2. monitoring Apr 07, 2026, 04:22 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Apr 07, 2026, 09:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 6, 2026

UCaaS: Call Parking Issue for small subset of D2 devices

Detected by Pingoru
Apr 06, 2026, 03:27 PM UTC
Resolved
Apr 06, 2026, 06:12 PM UTC
Duration
2h 44m
Affected: Call Completion
Timeline · 3 updates
  1. identified Apr 06, 2026, 03:27 PM UTC

    A subset of customers reported issues with call parking not functioning correctly. The root cause has been identified, and a remediation is being developed.

  2. monitoring Apr 06, 2026, 04:55 PM UTC

    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.

  3. resolved Apr 06, 2026, 06:12 PM UTC

    The issue affecting a limited number of D2 devices related to call parking has been resolved. The root cause was identified as a firmware defect, and affected devices have been remediated. All services are operating normally, and no broader impact to the UCaaS platform was observed. We will continue to monitor to ensure ongoing stability.

Read the full incident report →

Major April 2, 2026

UCaaS: Management Portal Outage

Detected by Pingoru
Apr 02, 2026, 06:19 PM UTC
Resolved
Apr 03, 2026, 12:41 AM UTC
Duration
6h 22m
Affected: UC Management Portal
Timeline · 3 updates
  1. investigating Apr 02, 2026, 06:19 PM UTC

    We are investigating an issue impacting the UCaaS Management Portal.

  2. monitoring Apr 02, 2026, 07:39 PM UTC

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

  3. resolved Apr 03, 2026, 12:41 AM UTC

    This issue has been resolved and Management Portal is working without any further issue.

Read the full incident report →

Critical April 2, 2026

UCaaS: Management Portal Unavailable

Detected by Pingoru
Apr 02, 2026, 05:23 PM UTC
Resolved
Apr 02, 2026, 06:12 PM UTC
Duration
48m
Affected: UC Management Portal
Timeline · 3 updates
  1. investigating Apr 02, 2026, 05:23 PM UTC

    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.

  2. monitoring Apr 02, 2026, 05:53 PM UTC

    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.

  3. resolved Apr 02, 2026, 06:12 PM UTC

    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, and a plan is in place to increase capacity to prevent recurrence.

Read the full incident report →

Major March 25, 2026

UCaaS: Voice Traffic Impacted

Detected by Pingoru
Mar 25, 2026, 05:59 PM UTC
Resolved
Mar 25, 2026, 06:35 PM UTC
Duration
35m
Affected: Call Completion
Timeline · 3 updates
  1. investigating Mar 25, 2026, 05:59 PM UTC

    We are experiencing intermittent network disruptions impacting call completion. We are currently investigating the issue.

  2. monitoring Mar 25, 2026, 06:05 PM UTC

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

  3. resolved Mar 25, 2026, 06:35 PM UTC

    Resolved: The upstream routing issue appears resolved. Call completion is operating within normal thresholds. Root cause is under investigation.

Read the full incident report →

Major March 20, 2026

UCaaS: Partial Outbound Call Failures

Detected by Pingoru
Mar 20, 2026, 03:19 PM UTC
Resolved
Mar 20, 2026, 08:48 PM UTC
Duration
5h 28m
Affected: Call Completion
Timeline · 4 updates
  1. investigating Mar 20, 2026, 03:19 PM UTC

    We are investigating a partial outbound call failure for a subset of customers.

  2. monitoring Mar 20, 2026, 04:39 PM UTC

    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.

  3. monitoring Mar 20, 2026, 06:45 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 20, 2026, 08:48 PM UTC

    There are no observed reports of outbound/inbound call failures. This issue is now resolved.

Read the full incident report →

Major March 20, 2026

UCaaS: Partial Inbound Call Failure

Detected by Pingoru
Mar 20, 2026, 01:59 PM UTC
Resolved
Mar 20, 2026, 02:53 PM UTC
Duration
53m
Affected: Call Completion
Timeline · 3 updates
  1. investigating Mar 20, 2026, 01:59 PM UTC

    We are experiencing partial inbound/outbound call failures. We are currently investigating.

  2. monitoring Mar 20, 2026, 02:35 PM UTC

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

  3. resolved Mar 20, 2026, 02:53 PM UTC

    This issue has been resolved. A fix was implemented for the call routing node failure, and inbound and outbound call completion are now functioning correctly.

Read the full incident report →

Major March 6, 2026

UCaaS: Intermittent Inbound / Outbound Call Failures

Detected by Pingoru
Mar 06, 2026, 08:46 PM UTC
Resolved
Mar 06, 2026, 10:24 PM UTC
Duration
1h 38m
Affected: Call Completion
Timeline · 5 updates
  1. investigating Mar 06, 2026, 08:46 PM UTC

    Some of the inbound / outbound calls from our system experiencing intermittent failures. We are currently trying to identify the root cause.

  2. investigating Mar 06, 2026, 09:23 PM UTC

    We are continue to investigate the issue.

  3. monitoring Mar 06, 2026, 09:52 PM UTC

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

  4. monitoring Mar 06, 2026, 09:54 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 06, 2026, 10:24 PM UTC

    This issue has been resolved.

Read the full incident report →

Major March 3, 2026

UCaaS: Inbound Call Failures Impacting Subset of Customers

Detected by Pingoru
Mar 03, 2026, 02:37 PM UTC
Resolved
Mar 03, 2026, 04:21 PM UTC
Duration
1h 44m
Affected: Call Completion
Timeline · 5 updates
  1. investigating Mar 03, 2026, 02:37 PM UTC

    We are currently investigating a higher number of inbound call failures that may impact subset our customers.

  2. investigating Mar 03, 2026, 02:38 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 03, 2026, 03:04 PM UTC

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

  4. monitoring Mar 03, 2026, 03:17 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Mar 03, 2026, 04:21 PM UTC

    All inbound calls are working.

Read the full incident report →

Critical February 28, 2026

ControlOne Services Impact in the US-MidWest (ORD) Region

Detected by Pingoru
Feb 28, 2026, 05:45 AM UTC
Resolved
Feb 28, 2026, 06:45 AM UTC
Duration
1h
Affected: US-MidWest (ORD) Region
Timeline · 3 updates
  1. investigating Feb 28, 2026, 05:45 AM UTC

    We are currently investigating an issue impacting services in our MidWest - ORD - Chicago Region.

  2. monitoring Feb 28, 2026, 07:50 AM UTC

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

  3. resolved Feb 28, 2026, 07:51 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 5, 2026

ControlOne Partial Service Degradation Due to Carrier Issue in US-SouthEast (ATL) Region

Detected by Pingoru
Feb 05, 2026, 10:52 PM UTC
Resolved
Feb 06, 2026, 02:02 AM UTC
Duration
3h 9m
Affected: US-SouthEast (ATL) Region
Timeline · 5 updates
  1. investigating Feb 05, 2026, 10:52 PM UTC

    We have identified and are currently monitoring widespread connectivity issues affecting multiple end-user ISPs in the US-SouthEast (ATL) region. Users may experience intermittent connection problems, packet loss, or increased latency when connecting to ControlOne services. Our Network Operations Center (NOC) is actively working to mitigate these issues by: - Implementing dynamic routing adjustments - Prioritizing critical traffic paths - Coordinating with affected ISPs to identify resolution timelines

  2. identified Feb 05, 2026, 11:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Feb 06, 2026, 12:45 AM UTC

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

  4. monitoring Feb 06, 2026, 12:45 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 06, 2026, 02:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Cytracom downtime and outages?

Pingoru polls Cytracom's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cytracom reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cytracom alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cytracom for free

5 free monitors · No credit card required