Historial de interrupciones de Cytracom

1. September 6, 2026 at 3:09 AM UTCinvestigating

   Estamos investigando un problema que está causando el portal de gestión de ControlOne y API de gestión de dispositivos para responder a solicitudes más lentamente de lo habitual. El portal de gestión puede parecer poco responsable, y los agentes de ControlOne que intentan conectar pueden experimentar dificultades de conexión.

2. September 6, 2026 at 3:24 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. September 6, 2026 at 3:39 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. September 6, 2026 at 5:05 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 2, 2026 at 6:48 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a llamadas de entrada para algunos clientes. La interrupción está relacionada con una falla de la red de fibra que impacta a uno de nuestros proveedores de servicios de corriente avanzada. Nuestro equipo está trabajando activamente con el proveedor para supervisar la recuperación y restaurar la llamada de entrada normal lo más rápido posible. Actualmente no se impactan las llamadas de salida (a menos que se dirijan a través de este proveedor) y otros servicios. Proporcionaremos actualizaciones adicionales a medida que se disponga de más información.

2. September 2, 2026 at 7:08 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 2, 2026 at 7:58 PM UTCidentified

   Hemos identificado la fuente de caídas de llamadas intermitentes que afectan a un subconjunto de clientes. Nuestro transportista de voz ha confirmado un incidente de red causando pérdida de paquetes en una porción de tráfico de voz. Esto está dando lugar a llamadas inbound intermitentemente que no sonar o caer poco después de la conexión. Nuestro operador está trabajando activamente para restaurar el comportamiento normal de llamadas, y estamos monitoreando de cerca la calidad de las llamadas en las cuentas afectadas. Vamos a proporcionar actualizaciones ya que tenemos más información.

4. September 3, 2026 at 1:49 PM UTCmonitoring

   Nuestro transportista de corriente avanzada está observando el comportamiento de llamada esperado y seguirá monitoreando para la estabilidad.

5. September 3, 2026 at 6:58 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 2, 2026 at 4:07 PM UTCinvestigating

   Actualmente estamos investigando una degradación parcial de los servicios en la región de Estados Unidos-Sur (LAX). Algunos clientes están experimentando mayor latencia normal y conectividad intermitente.

2. September 2, 2026 at 7:49 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. September 3, 2026 at 12:54 PM UTCresolved

   Se ha reparado un corte de fibra de terceros que afecta a múltiples rutas de red de transportistas regionales en el sur de California, y se han restaurado los servicios.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 28, 2026 at 5:29 PM UTCinvestigating

   Actualmente estamos investigando una degradación parcial de los servicios en la región de Estados Unidos-Sur (ATL) que impacta la conectividad de puentes para un subconjunto de clientes.

2. August 28, 2026 at 7:57 PM UTCmonitoring

   Las cargas de trabajo repercutidas se han programado para alternar los anfitriones de computación y estamos monitoreando los resultados. El hardware impactado se someterá a acciones de remediación para los componentes físicos afectados.

3. August 28, 2026 at 11:36 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 12:44 PM UTCinvestigating

   Actualmente estamos investigando una degradación parcial de los servicios en la región de Estados Unidos-Sur (LAX) que impacta la conectividad de puentes para un subconjunto de clientes.

2. August 19, 2026 at 1:18 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. August 19, 2026 at 5:10 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 14, 2026 at 12:33 PM UTCidentified

   We have identified an issue affecting ControlOne Agent geolocation services. Agents may intermittently fail a location in the portal, or fail a device posture check that requires a location fix. As a workaround partners can remove geolocation from the policy.

2. August 14, 2026 at 12:47 PM UTCmonitoring

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

3. August 14, 2026 at 2:34 PM UTCresolved

   This incident has been resolved.

1. August 13, 2026 at 8:10 PM UTCinvestigating

   Actualmente estamos investigando un problema que hace que un subconjunto de sitios de ControlOne reporte un estado ISP incorrecto en el portal ControlOne. Este es un problema visual solamente y no impacta la conectividad del sitio.

2. August 13, 2026 at 9:06 PM UTCidentified

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

3. August 13, 2026 at 10:09 PM UTCmonitoring

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

4. August 14, 2026 at 2:22 AM UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 11, 2026 at 1:29 PM UTCinvestigating

   We are currently investigating a partial service degradation in the US-Southeast (ATL) Region.

2. August 11, 2026 at 4:55 PM UTCmonitoring

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

3. August 11, 2026 at 7:47 PM UTCresolved

   This incident has been resolved.

1. August 7, 2026 at 9:18 PM UTCidentified

   We are investigating an issue that is causing ControlOne's Management portal and device management API to respond to configuration changes more slowly than usual. The management portal may appear unresponsive until this clears.

2. August 7, 2026 at 9:57 PM UTCresolved

   This incident has been resolved.

1. July 30, 2026 at 6:10 PM UTCidentified

   Estamos investigando un problema que impacta las fallas de llamadas de entrada y salida. Identificamos una configuración incorrecta que causó este problema. Estamos trabajando en una solución y se actualizará pronto.

2. July 30, 2026 at 6:16 PM UTCmonitoring

   Se ha implementado una solución y las llamadas fluyen como siempre. Estamos monitoreando de cerca cualquier otra cuestión.

3. July 30, 2026 at 9:25 PM UTCresolved

   Este incidente ha sido resuelto. Hemos implementado un paso adicional para que la gestión automatizada de config no se active fuera de una ventana de mantenimiento declarada. Nos disculpamos por la perturbación causada por esto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 30, 2026 at 3:36 PM UTCinvestigating

   Hemos identificado un problema que causa una degradación parcial de los servicios para un subconjunto de clientes en la región de US-SouthCentral ControlOne. ControlOne Bridges puede experimentar conectividad intermitente ControlOne Agents puede experimentar conectividad intermitente o estado "Retrying"

2. July 30, 2026 at 4:07 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 30, 2026 at 9:55 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 1:44 PM UTCinvestigating

   Hemos identificado un problema que causa una degradación parcial de los servicios para un subconjunto del 15% de los clientes en la región US-Southeast ControlOne. ControlOne Bridges puede experimentar conectividad intermitente ControlOne Agents puede experimentar conectividad intermitente o estado "Retrying"

2. July 21, 2026 at 2:12 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. July 22, 2026 at 4:12 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 5:53 PM UTCinvestigating

   One of the servers in our fleet experiencing network connectivity issues and our engineering team is investigating. If you are in that server, you may experience intermittent call failures. We will resolve this quickly and thanks for your patience.

2. July 9, 2026 at 5:55 PM UTCmonitoring

   We restarted the network interface and the calls should flow as usual. Thanks for your patience during this issue.

3. July 9, 2026 at 6:05 PM UTCresolved

   This incident has been resolved.

1. July 7, 2026 at 5:17 PM UTCinvestigating

   We are currently investigating an issue causing partial inbound and outbound call failures for some customers. Affected users may experience failed call attempts, delayed call setup, or intermittent call completion issues. The issue does not appear to impact all calls or all customers. Our engineering team is actively investigating and working to restore full calling functionality. We will provide additional updates as more information becomes available.

2. July 7, 2026 at 5:35 PM UTCmonitoring

   We have taken corrective action to address the partial inbound and outbound call failures affecting some customers. A small number of call processing servers were restarted to restore normal call flow. Call traffic has recovered, and we are currently monitoring the platform to confirm continued stability. Some users may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident. We will continue monitoring and provide a final update once the issue is fully resolved.

3. July 7, 2026 at 9:48 PM UTCresolved

   The issue causing partial inbound and outbound call failures has been resolved. Corrective action was taken by restarting a small number of call processing servers, which restored normal call flow. After continued monitoring, inbound and outbound calling have remained stable. Some customers may have experienced failed call attempts, delayed call setup, or intermittent call completion issues during the incident window. We apologize for the disruption and appreciate your patience while our team worked to restore service.

1. June 29, 2026 at 3:24 PM UTCinvestigating

   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.

2. June 29, 2026 at 4:33 PM UTCidentified

   **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 continue to route and complete normally. We expect the Realtime Call Center dashboard to be current within the next hour.

3. June 29, 2026 at 5:02 PM UTCmonitoring

   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 statistics should display as usual starting tomorrow.

4. June 30, 2026 at 7:45 AM UTCresolved

   This issue has been resolved.

1. June 10, 2026 at 6:43 PM UTCidentified

   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.

2. June 10, 2026 at 8:50 PM UTCmonitoring

   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.

3. June 11, 2026 at 11:34 AM UTCresolved

   All backlog Call Details Records have been processed. This issue is now resolved.

1. June 9, 2026 at 8:32 PM UTCidentified

   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.

2. June 9, 2026 at 9:44 PM UTCmonitoring

   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.

3. June 10, 2026 at 2:04 AM UTCresolved

   The backlog processing has been completed. This issue is now resolved.

1. June 3, 2026 at 3:10 PM UTCinvestigating

   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.

2. June 3, 2026 at 3:49 PM UTCmonitoring

   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.

3. June 4, 2026 at 4:06 AM UTCresolved

   This incident has been resolved.

1. June 2, 2026 at 4:11 PM UTCinvestigating

   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.

2. June 2, 2026 at 4:49 PM UTCmonitoring

   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.

3. June 2, 2026 at 8:56 PM UTCmonitoring

   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.

4. June 2, 2026 at 8:57 PM UTCresolved

   This incident has been resolved.

1. May 29, 2026 at 6:41 PM UTCidentified

   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.

2. May 29, 2026 at 9:02 PM UTCmonitoring

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

3. May 29, 2026 at 11:27 PM UTCresolved

   The CNAM (Caller ID) service is fully functional without any performance constraints.