Istoricul incidentelor Cytracom

1. 6 septembrie 2026 la 03:09 UTCinvestigating

   Investigăm o problemă care face ca API-ul de management al departamentului să răspundă mai încet decât de obicei. Portalul de management poate părea neresponsabil, și ControlOne agenți care încearcă să se conecteze pot experimenta dificultăți de conectare.

2. 6 septembrie 2026 la 03:24 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 6 septembrie 2026 la 03:39 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 6 septembrie 2026 la 05:05 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 septembrie 2026 la 18:48 UTCinvestigating

   Investigăm în prezent o problemă care afectează apelurile de intrare pentru unii clienți. Perturbaţia este legată de o defecţiune a reţelei de fibre care afectează unul dintre furnizorii noştri de servicii din amonte. Echipa noastră lucrează activ cu furnizorul pentru a monitoriza recuperarea și a restabili apelul normal de intrare cât mai repede posibil. Apelul de ieșire (cu excepția cazului în care rutat prin acest furnizor) și alte servicii nu sunt afectate în prezent. Vom furniza actualizări suplimentare pe măsură ce devin disponibile mai multe informații.

2. 2 septembrie 2026 la 19:08 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 2 septembrie 2026 la 19:58 UTCidentified

   Am identificat sursa de picături intermitente de apel care afectează un subset de clienți. Portavionul nostru vocal din amonte a confirmat un incident de rețea care cauzează pierderi de pachete pe o parte din traficul de voce. Acest lucru duce la apeluri de intrare intermitente care nu reușesc să sune prin sau în scădere la scurt timp după conexiune. Transportatorul nostru lucrează în mod activ pentru a restabili comportamentul normal de apelare, şi monitorizăm îndeaproape calitatea apelurilor în conturile afectate. Vom furniza actualizări deoarece avem mai multe informații.

4. 3 septembrie 2026 la 13:49 UTCmonitoring

   Transportorul nostru din amonte observă comportamentul de asteptare si va continua să monitorizeze stabilitatea.

5. 3 septembrie 2026 la 18:58 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 2 septembrie 2026 la 16:07 UTCinvestigating

   Investigăm în prezent o degradare parţială a serviciilor în regiunea SUA-Vestul de Sud (LAX). Unii clienți se confruntă cu o latență mai mare decât normală și conectivitate intermitentă.

2. 2 septembrie 2026 la 19:49 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 3 septembrie 2026 la 12:54 UTCresolved

   A fost reparată o tăiere de fibră terţă parte care afectează mai multe căi regionale de transport din sudul Californiei, iar serviciile au fost restaurate.

Traducere automată din actualizarea oficială a incidentului.

1. 28 august 2026 la 17:29 UTCinvestigating

   În prezent investigăm o degradare parţială a serviciilor în regiunea SUA-Southeastern (ATL) care afectează conectivitatea podului pentru un subset de clienţi.

2. 28 august 2026 la 19:57 UTCmonitoring

   Volumul de muncă afectat a fost reprogramat pentru a alterna gazdele de calcul și monitorizăm rezultatele. hardware-ul afectat va fi supus unor acțiuni de remediere pentru componentele fizice afectate.

3. 28 august 2026 la 23:36 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 19 august 2026 la 12:44 UTCinvestigating

   Investigăm în prezent o degradare parţială a serviciilor în regiunea SUA-SouthWest (LAX) care afectează conectivitatea podului pentru un subset de clienţi.

2. 19 august 2026 la 13:18 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 19 august 2026 la 17:10 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 14 august 2026 la 12:33 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. 14 august 2026 la 12:47 UTCmonitoring

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

3. 14 august 2026 la 14:34 UTCresolved

   This incident has been resolved.

1. 13 august 2026 la 20:10 UTCinvestigating

   We are currently investigating an issue causing a subset of ControlOne Sites to report an incorrect ISP status in the ControlOne portal. This is a visual problem only and does not impact site connectivity.

2. 13 august 2026 la 21:06 UTCidentified

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

3. 13 august 2026 la 22:09 UTCmonitoring

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

4. 14 august 2026 la 02:22 UTCresolved

   This incident has been resolved.

1. 11 august 2026 la 13:29 UTCinvestigating

   Investigăm în prezent o degradare parţială a serviciilor în regiunea SUA-Southeastern (ATL).

2. 11 august 2026 la 16:55 UTCmonitoring

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

3. 11 august 2026 la 19:47 UTCresolved

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 7 august 2026 la 21:18 UTCidentified

   Investigăm o problemă care cauzează API-ul de Management al ControlOne pentru a răspunde la schimbările de configurare mai lent decât de obicei. Portalul de management poate părea neresponsabil până când acest lucru se șterge.

2. 7 august 2026 la 21:57 UTCresolved

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 18:10 UTCidentified

   Investigăm o problemă care afectează eşecurile apelurilor. Am identificat o configuraţie incorectă care a cauzat această problemă. Lucrăm la un fix și va actualiza în curând.

2. 30 iulie 2026 la 18:16 UTCmonitoring

   Un fix a fost implementat și noi apelurile curge ca de obicei. Monitorizăm îndeaproape orice alte aspecte.

3. 30 iulie 2026 la 21:25 UTCresolved

   Acest incident a fost rezolvat. Am implementat un pas în plus, astfel încât managementul automat de configurare nu declanşează în afara unei ferestre de întreţinere declarate. Ne cerem scuze pentru deranjul cauzat de asta.

Traducere automată din actualizarea oficială a incidentului.

1. 30 iulie 2026 la 15:36 UTCinvestigating

   Am identificat o problemă care cauzează o degradare parţială a serviciilor pentru un subset de clienţi din regiunea SUA-SouthCentral ControlOne. ControlOne Bridges poate experimenta conectivitate intermitentă ControlOne Agents poate experimenta conectivitate intermitentă sau "retrying" status

2. 30 iulie 2026 la 16:07 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 30 iulie 2026 la 21:55 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 13:44 UTCinvestigating

   Am identificat o problemă care cauzează o degradare parţială a serviciului pentru un subgrup de 15% dintre clienţi din regiunea SUA-Southeastern ControlOne. ControlOne Bridges poate experimenta conectivitate intermitentă ControlOne Agents poate experimenta conectivitate intermitentă sau "retrying" status

2. 21 iulie 2026 la 14:12 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 22 iulie 2026 la 04:12 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iulie 2026 la 17:53 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. 9 iulie 2026 la 17:55 UTCmonitoring

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

3. 9 iulie 2026 la 18:05 UTCresolved

   This incident has been resolved.

1. 7 iulie 2026 la 17:17 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. 7 iulie 2026 la 17:35 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. 7 iulie 2026 la 21:48 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. 29 iunie 2026 la 15:24 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. 29 iunie 2026 la 16:33 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. 29 iunie 2026 la 17:02 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. 30 iunie 2026 la 07:45 UTCresolved

   This issue has been resolved.

1. 10 iunie 2026 la 18:43 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. 10 iunie 2026 la 20:50 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. 11 iunie 2026 la 11:34 UTCresolved

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

1. 9 iunie 2026 la 20:32 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. 9 iunie 2026 la 21:44 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. 10 iunie 2026 la 02:04 UTCresolved

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

1. 3 iunie 2026 la 15:10 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. 3 iunie 2026 la 15:49 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. 4 iunie 2026 la 04:06 UTCresolved

   This incident has been resolved.

1. 2 iunie 2026 la 16:11 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. 2 iunie 2026 la 16:49 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. 2 iunie 2026 la 20:56 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. 2 iunie 2026 la 20:57 UTCresolved

   This incident has been resolved.

1. 29 mai 2026 la 18:41 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. 29 mai 2026 la 21:02 UTCmonitoring

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

3. 29 mai 2026 la 23:27 UTCresolved

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