Cytracom driftsforstyrrelser

1. 6. september 2026 kl. 03.09 UTCinvestigating

   Vi undersøger et problem, der forårsager ControlOne 's Management portal og enhedsstyring API til at reagere på anmodninger langsommere end normalt. Management portalen kan synes ulydhør, og ControlOne Agenter forsøger at forbinde kan opleve problemer forbindelse.

2. 6. september 2026 kl. 03.24 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 6. september 2026 kl. 03.39 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 6. september 2026 kl. 05.05 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 18.48 UTCinvestigating

   Vi undersøger i øjeblikket et problem, der påvirker indgående opkald til nogle kunder. Afbrydelsen er relateret til en fiber netværk fiasko påvirker en af vores opstrømsserviceudbydere. Vores team arbejder aktivt sammen med udbyderen for at overvåge inddrivelse og genoprette normal indgående opkald så hurtigt som muligt. Udgående opkald (medmindre drevet gennem denne udbyder) og andre tjenester er ikke i øjeblikket påvirket. Vi vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

2. 2. september 2026 kl. 19.08 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 2. september 2026 kl. 19.58 UTCidentified

   Vi har identificeret kilden til intermitterende indgående opkald dråber påvirker en delmængde af kunder. Vores opstrøms voice carrier har bekræftet et netværk hændelse forårsager pakketab på en del af taletrafikken. Dette resulterer i indgående opkald, der periodisk ikke ringer igennem eller falder kort efter forbindelsen. Vores luftfartsselskab arbejder aktivt på at genoprette normal calling adfærd, og vi er tæt på at overvåge call kvalitet på tværs af berørte konti. Vi vil levere opdateringer, da vi har flere oplysninger.

4. 3. september 2026 kl. 13.49 UTCmonitoring

   Vores opstrømsholder observerer forventet opkaldsadfærd og vil fortsætte med at overvåge for stabilitet.

5. 3. september 2026 kl. 18.58 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 16.07 UTCinvestigating

   Vi undersøger i øjeblikket en delvis forringelse af tjenesten i US- SouthWest (LAX) regionen. Nogle kunder oplever højere latenstid og intermitterende forbindelser.

2. 2. september 2026 kl. 19.49 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 3. september 2026 kl. 12.54 UTCresolved

   En tredje part fiber snit påvirker flere regionale luftfartsselskab netveje i det sydlige Californien er blevet repareret, og tjenester er blevet restaureret.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. august 2026 kl. 17.29 UTCinvestigating

   Vi er i øjeblikket ved at undersøge en delvis service nedbrydning i US- Southeast (ATL) Region påvirker bro forbindelse for en delmængde af kunder.

2. 28. august 2026 kl. 19.57 UTCmonitoring

   Implementerede arbejdsbelastninger er blevet flyttet til alternative computerværter, og vi overvåger resultaterne. Den ramte hardware vil gennemgå oprensning handlinger for de berørte fysiske komponenter.

3. 28. august 2026 kl. 23.36 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. august 2026 kl. 12.44 UTCinvestigating

   Vi er i øjeblikket ved at undersøge en delvis service nedbrydning i US- SouthWest (LAX) Region påvirker bro forbindelse for en delmængde af kunder.

2. 19. august 2026 kl. 13.18 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 19. august 2026 kl. 17.10 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 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 kl. 12.47 UTCmonitoring

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

3. 14. august 2026 kl. 14.34 UTCresolved

   This incident has been resolved.

1. 13. august 2026 kl. 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 kl. 21.06 UTCidentified

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

3. 13. august 2026 kl. 22.09 UTCmonitoring

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

4. 14. august 2026 kl. 02.22 UTCresolved

   This incident has been resolved.

1. 11. august 2026 kl. 13.29 UTCinvestigating

   Vi undersøger i øjeblikket en delvis forringelse af tjenesten i US- Sydøst (ATL) regionen.

2. 11. august 2026 kl. 16.55 UTCmonitoring

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

3. 11. august 2026 kl. 19.47 UTCresolved

   This incident has been resolved.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. august 2026 kl. 21.18 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. 7. august 2026 kl. 21.57 UTCresolved

   This incident has been resolved.

1. 30. juli 2026 kl. 18.10 UTCidentified

   Vi undersøger et problem, der påvirker indgående og udgående opkald. Vi identificerede en forkert konfiguration, der forårsagede dette problem. Vi arbejder på et fix og vil snart opdatere.

2. 30. juli 2026 kl. 18.16 UTCmonitoring

   Et fix er blevet gennemført, og vi ringer som sædvanlig. Vi overvåger nøje alle andre spørgsmål.

3. 30. juli 2026 kl. 21.25 UTCresolved

   Denne hændelse er blevet løst. Vi har implementeret et ekstra trin, så den automatiserede config management ikke udløser uden for et erklæret vedligeholdelsesvindue. Vi undskylder forstyrrelsen som følge af dette.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juli 2026 kl. 15.36 UTCinvestigating

   Vi har identificeret et problem, der forårsager en delvis forringelse af tjenesten for en undergruppe af kunder i US- SouthCentral ControlOne regionen. ControlOne Bridges kan opleve intermitterende forbindelse ControlOne Agenter kan opleve intermitterende forbindelse eller "Genopsætning" status

2. 30. juli 2026 kl. 16.07 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 30. juli 2026 kl. 21.55 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. juli 2026 kl. 13.44 UTCinvestigating

   Vi har identificeret et problem, der forårsager en delvis forringelse af tjenesten for en 15% undergruppe af kunder i US- Southeast ControlOne regionen. ControlOne Bridges kan opleve intermitterende forbindelse ControlOne Agenter kan opleve intermitterende forbindelse eller "Genopsætning" status

2. 21. juli 2026 kl. 14.12 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 22. juli 2026 kl. 04.12 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 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. juli 2026 kl. 17.55 UTCmonitoring

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

3. 9. juli 2026 kl. 18.05 UTCresolved

   This incident has been resolved.

1. 7. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 07.45 UTCresolved

   This issue has been resolved.

1. 10. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 11.34 UTCresolved

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

1. 9. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 02.04 UTCresolved

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

1. 3. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 04.06 UTCresolved

   This incident has been resolved.

1. 2. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 20.57 UTCresolved

   This incident has been resolved.

1. 29. maj 2026 kl. 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. maj 2026 kl. 21.02 UTCmonitoring

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

3. 29. maj 2026 kl. 23.27 UTCresolved

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